[
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563219#comment-14563219
]
Albert P Tobey commented on CASSANDRA-7486:
-------------------------------------------
I tested a number of different pause targets on a wide variety of machines.
While the 200ms default is often fine on big machines with real CPUs, in
Ghz-constrained environments like EC2 PVM or LV Xeons, throughput dropped
considerably so that the GC could hit the pause target. I initially tested at
1000ms and 2000ms but settled on 500ms because it provides most of the benefit
of a more generous pause target while being far enough below the current
read/write timeouts in cassandra.yaml to make sure that pauses never/rarely hit
those limits.
> 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)
