[
https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933598#comment-14933598
]
Joshua McKenzie commented on CASSANDRA-10403:
---------------------------------------------
To me, the long-term solution of C* having the intelligence to select G1 for
heaps over X, CMS for heaps under X makes a lot of sense, assuming test data
shows that to be the appropriate solution.
I'd argue that what we need to do here is figure out what the sanest
recommendation is for a default GC on 3.0, get that setup in our launch scripts
(if necessary), and probably include the alternate set of GC configurations in
our launch files, commented out, so people can easily swap back and forth based
on their needs.
> 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)
