[jira] [Comment Edited] (CASSANDRA-10403) Consider reverting to CMS GC on 3.0

["Jonathan Shook (JIRA)" <ji...@apache.org>]

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

Jonathan Shook edited comment on CASSANDRA-10403 at 9/30/15 12:58 AM:
----------------------------------------------------------------------

Note about memory sizes. Everything I wrote above assumes that we are talking about smaller heaps. Things clearly change when we go up in heap size beyond what CMS can handle well. (for those reading from the middle)


was (Author: jshook):
Note about memory sizes. Everything I wrote above assumes that we are talking about smaller heaps. Things clearly change when we go up in heap size beyond what CMS can handle well.

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