cassandra-commits mailing list archives

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

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

Paulo Motta edited comment on CASSANDRA-10403 at 9/30/15 3:59 PM:
------------------------------------------------------------------

I will hold back the experiments a bit to work on some other ickets until we decide whether
it's worth comparing CMS vs G1 for small heap sizes in the context of this ticket, or we can
just decide based on discussion.

edit: seems I pressed enter without completing the message before, sorry for that.


was (Author: pauloricardomg):
I will hold back the experiments 

> 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