[
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563034#comment-14563034
]
Joshua McKenzie commented on CASSANDRA-7486:
--------------------------------------------
Seems reasonable to me and glad to have that documented in the ticket (hint
hint).
Last question I have before commit is for [~ato...@datastax.com] (though
anyone's welcome to chime in): Why did we settle on 500ms for our
MaxGCPauseMillis? Was that also part of an offline conversation, or are we just
rolling with the #'s Michael used above? Do we have any test data to show that
500 is a solid default for our use case rather than the pre-packaged 200 for g1
or the 2000 you'd used above for some testing?
> 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
> Assignee: Albert P Tobey
> Fix For: 3.0 beta 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)
