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, 14 Oct 2015 13:58:06 GMT


Joshua McKenzie commented on CASSANDRA-10403:

Sorry for the delay - thought we were waiting on the answer re: package install.

.ps1 changes look good and test correctly. Only one thing left: the GC logging options in
jvm.options won't work on Windows if users un-comment those lines as-is. We should probably
have a little logic in cassandra-env.* to parse out GC logging options and a simple flag to
enable it in the jvm.options file. This shouldn't necessitate a change to the regex/StartsWith
checks since the lines start with JVM_OPTIONS, so it should be pretty clean.

Once that's ironed out, I'll commit.

> 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