[
https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949699#comment-14949699
]
Paulo Motta commented on CASSANDRA-10403:
-----------------------------------------
Thanks for the review! Follow-up below:
* Updated branch with windows support to jvm.options file on cassandra-env.ps1
* Removed legacy label from CMS settings on jvm.options file
* .bat already had CMS settings there
* I don't think it's necessary to have an alert/fail when no gc settings are
present on the jvm.options file, since that's a valid option (default gc
settings are picked), and if the user chooses to edit the file manually to
comment the GC options he better know what he's doing. :P
* Replaced G1 NEWS.txt entry with entry explaining gc options were moved to
jvm.options file
* Follow-up ticket created: CASSANDRA-10494
Do package installs need any tweaking to support the jvm.options file or
anything in the /conf dir is already supported?
> Consider reverting to CMS GC on 3.0
> -----------------------------------
>
> Key: CASSANDRA-10403
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10403
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Joshua McKenzie
> Assignee: Paulo Motta
> Fix For: 3.0.0 rc2
>
>
> Reference discussion on CASSANDRA-7486.
> For smaller heap sizes G1 appears to have some throughput/latency issues when
> compared to CMS. With our default max heap size at 8G on 3.0, there's a
> strong argument to be made for having CMS as the default for the 3.0 release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
