[
https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952154#comment-14952154
]
Jeff Jirsa commented on CASSANDRA-10403:
----------------------------------------
Being somewhat related to that anecdote (since it's my employer and I touch
those clusters every day), I'll point out that the cluster described in that
talk was tuned by [[email protected]], and when we tried to apply a similar
config to our 2.0 cluster, we started seeing a ton of OOMs with 2.0.x + G1 + 8G
heap. We eventually reverted, because we understood CMS better (already setup
with the 8150 tunings), and we were able to mitigate G1 OOMs on that 2.0
cluster with CMS. I think the reality is that both CMS and G1 need to be tuned
- in our case, we had tuned CMS on that 2.0 cluster. +1 to having G1 marked as
experimental but easy to enable.
> 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)
