cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-7486) Migrate to G1GC by default
Date Mon, 21 Sep 2015 15:41:07 GMT

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

Benedict edited comment on CASSANDRA-7486 at 9/21/15 3:40 PM:
--------------------------------------------------------------

Regrettably, that run crashed. Will have to diagnose the logs to see what may have happened
- [~EnigmaCurry], could you unstick the cstar job, and collect the log files?

(The weird thing about CMS on that particular run is that 2.2 does not degrade; it is still
40% faster)


was (Author: benedict):
Regrettably, that run crashed. Will have to diagnose the logs to see what may have happened
- [~EnigmaCurry], could you unstick the cstar job, and collect the log files?

> Migrate to G1GC by default
> --------------------------
>
>                 Key: CASSANDRA-7486
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7486
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Config
>            Reporter: Jonathan Ellis
>             Fix For: 3.0 alpha 1
>
>
> See http://www.slideshare.net/MonicaBeckwith/garbage-first-garbage-collector-g1-7486gc-migration-to-expectations-and-advanced-tuning
and https://twitter.com/rbranson/status/482113561431265281
> May want to default 2.1 to G1.
> 2.1 is a different animal from 2.0 after moving most of memtables off heap.  Suspect
this will help G1 even more than CMS.  (NB this is off by default but needs to be part of
the test.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message