[
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901846#comment-14901846
]
Ryan McGuire commented on CASSANDRA-7486:
-----------------------------------------
[~benedict] I modified the schedule GUI to allow you to change the version of
stress per operation. Just change the default 'apache/trunk' to
'enigmacurry/stress-report-interval' where I took your branch and applied a 4G
stress heap. If you want to tweak that, you can put your own branch name in
instead. The GC logs have been logged for awhile now, they're wrapped up in the
same tarball as the other logs that you can download.
See this example for how to specify your test:
http://cstar.datastax.com/schedule?clone=0c2efd50-60d5-11e5-b6a8-42010af0688f
> 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)
