[ https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933621#comment-14933621 ]
Jonathan Shook commented on CASSANDRA-10403: -------------------------------------------- I would be entirely in favor of having a separate settings file that can simply be sourced in. Having several related GC options sprinkled through the -env file is bothersome. This should apply as well to the CMS settings. Perhaps it should even be a soft setting, as long as the possible values are marshaled against any injection. > 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 > 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)