cassandra-commits mailing list archives

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


Sylvain Lebresne commented on CASSANDRA-10403:

My 2 cents here is: let's revert to CMS for 3.0 (while tweaking our startup script so it's
easier to switch setting as suggested above, that's a good idea and it should be trivial)
since that's been our default forever and it's clear we haven't experimented enough yet to
be 100% sure that G1 is a clearly better default and so we should err on the side of conservatism.
We absolutely should continue to experiment on this and refine our defaults and we now have
CASSANDRA-10425 for that. But as far as 3.0 is concerned, I would venture that using our available
resource for more testing (and things like testing performance of clusters during upgrade
to 3.0 to take just one example) would be a better choice that spending it on more experimentation
on this. Even if G1 turns out to be an overall better default, 3.2 will come only 2 months
after 3.0.

> 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