[
https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936982#comment-14936982
]
Joshua McKenzie commented on CASSANDRA-10403:
---------------------------------------------
>From [~benedict]'s
>[comment|https://issues.apache.org/jira/browse/CASSANDRA-7486?focusedCommentId=14899937&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14899937]
> on CASSANDRA-7486:
bq. for anything but the most write-heavy workloads an 8Gb heap is probably
what you'll want to ensure the file cache can make meaningful contributions to
performance.
[~jshook] / [~xedin]: Does your experience running C* in production back up
that assertion? It makes theoretical sense to me and would change the weighing
of large heap vs. small tuning in the JVM / our selection of defaults if so.
> 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)
