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 Mon, 28 Sep 2015 17:32:04 GMT


Joshua McKenzie commented on CASSANDRA-10403:

Adding extra configuration files w/options to switch on launch is something I'd be comfortable
with us adding after GA so long as we leave our default alone. For this ticket, let's focus
on just determining whether or not we feel reverting from G1 to CMS is appropriate for 3.0,
and then move forward on a separate ticket for adding more intelligence to our GC configuration
sourcing options.

For the record and my .02, I quite like the idea of us having multiple GC profiles out of
the box with either logic to switch based on available heap, or via command-line for different
expected workloads for instance; I think there's a lot we could do there to make operators'
lives easier.

[~enigmacurry]: Any update on how that 100x test went?

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

View raw message