[
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523736#comment-14523736
]
Benedict commented on CASSANDRA-7486:
-------------------------------------
bq. there is a new-ish setting to enable parallel reference collection
Throughput was something like 5% of other collectors in my testing, so
parallelizing this would only help so much! :)
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.
> Compare CMS and G1 pause times
> ------------------------------
>
> Key: CASSANDRA-7486
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7486
> Project: Cassandra
> Issue Type: Test
> Components: Config
> Reporter: Jonathan Ellis
> Assignee: Shawn Kumar
> Fix For: 2.1.x
>
>
> 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)
