[
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562936#comment-14562936
]
Joshua McKenzie commented on CASSANDRA-7486:
--------------------------------------------
bq. My point is, we don't really fully understand G1, and unless we undertake a
research project to fully understand its pathological cases, and how they
compare/contrast to its history, I'd prefer we ensured it behaved under complex
loads, and not just under isolated read or write loading.
bq. Al, we're on board with making G1 the default for 3.0 (which incidentally
requires java 8), if you can post a patch.
[~benedict] and [~jbellis]: Reconcile these two statements for me as there
don't appear to be updates on this ticket that bridge them. Were there
discussions on IRC / offline or do you still have outstanding concerns about
pathological cases w/this collector Benedict?
> 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)
