[
https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936112#comment-14936112
]
Paulo Motta commented on CASSANDRA-10403:
-----------------------------------------
I will perform some saturation tests on trunk comparing default CMS settings
(from 2.2) vs default G1 settings (from 3.0) with read, write and mixed
workloads with the latest oracle jvm8. I will also perform operations such as
repairs and bootstraps during the benchmarks in order to simulate a
production-ish environment.
Since the previous tests were done with SSD boxes, I will start the experiments
with m1.xlarge spindle instances in order to exhaust disk capacity more easily
and generate additional heap pressure, so things will go more insane. What do
you think [~JoshuaMcKenzie]? Please let me know if this sounds good, or if any
additional scenarios should be covered.
If there are clear impacts on these experiments, then we can consider rolling
back and provide commented-out G1 options for larger heap sizes. Otherwise, we
might as well just leave G1 enabled by default, since there was already a lot
of discussion (as well as experiments on larger heap sizes, non-default GC
settings and steady-state workloads) on CASSANDRA-7486.
> 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)
