cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10403) Consider reverting to CMS GC on 3.0
Date Wed, 30 Sep 2015 18:03:04 GMT


Joshua McKenzie commented on CASSANDRA-10403:

The debate here isn't between "Do we consider G1 or disregard G1 entirely", but rather "Do
we use CMS or G1 as our default GC for 3.0, keeping the settings for the alternative available
in our configuration files for users to swap between easily".

[~enigmacurry]: did we ever get that 100x test run to complete successfully? Before we determine
whether Paulo should go fully down this rabbit-hole pre 3.0 releasing, I'd like that data
point since we invested some effort into getting that running already.

> Consider reverting to CMS GC on 3.0
> -----------------------------------
>                 Key: CASSANDRA-10403
>                 URL:
>             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

View raw message