[ 
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520071#comment-14520071
 ] 

Jonathan Ellis edited comment on CASSANDRA-7486 at 4/29/15 7:53 PM:
--------------------------------------------------------------------

> IMO consistent performance should always take precedence over maximum 
> performance/throughput.

Agreed.  I think our bar here should be "Is G1 better for the average user" 
keeping in mind that the average user is a *lot* worse at tuning CMS than 
Ariel.  Power users can tune for their own workload the way they always have.

(Edit: this is not to say that more testing is not warranted, but let's 
approach this from, "if we were choosing a default today what would we do" and 
not "let's not switch unless we can prove that G1 is always better everywhere.")


was (Author: jbellis):
> IMO consistent performance should always take precedence over maximum 
> performance/throughput.

Agreed.  I think our bar here should be "Is G1 better for the average user" 
keeping in mind that the average user is a *lot* worse at tuning CMS than 
Ariel.  Power users can tune for their own workload the way they always have.

> 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)

Reply via email to