[
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901127#comment-14901127
]
Benedict commented on CASSANDRA-7486:
-------------------------------------
[~enigmacurry]: could you upgrade stress to run from [this
branch|https://github.com/belliottsmith/cassandra/tree/stress-report-interval]?
Could you also ensure it's running with a largeish heap (at least a couple of
Gb)? I'll file tickets to update the mainline source tree on both these counts.
We should start enabling stress gc logging in cstar at some point as well, so
we can diagnose issues in the run, and see if they're attributable to stress
itself.
> 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)
