cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Shook (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-10403) Consider reverting to CMS GC on 3.0
Date Wed, 30 Sep 2015 19:46:05 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938731#comment-14938731
] 

Jonathan Shook edited comment on CASSANDRA-10403 at 9/30/15 7:45 PM:
---------------------------------------------------------------------

To simplify, implementing CASSANDRA-10425 is effectively the same as reverting for the systems
that we have commonly tested for, while allowing a likely better starting point for those
that we have field experience with G1.


was (Author: jshook):
To simplify, implementing CASSANDRA-10425 is effectively the same as reverting for the system
that we have tested for, while allowing a likely better starting point for those that we have
field experience with G1.

> 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)

Mime
View raw message