cassandra-commits mailing list archives

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

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

Pavel Yaskevich commented on CASSANDRA-7486:
--------------------------------------------

Thanks, Benedict! This is in line with what I would expect from longer run of CMS vs. G1 since
CMS is known to degrade over time and G1 actually needs some time to collect statistics and
properly arrange relocations etc., so let's wait with revert and see what would 100x larger
run produce.

> 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