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

Albert P Tobey commented on CASSANDRA-7486:
-------------------------------------------

This is with 2.0 / OpenJDK8 since that's what I had running. Same everything 
each run except for heap size. cassandra-stress 2.1.4 read workload / 800 
threads. I'll re-run with 2.1 / Oracle JDK8 and some mixed load.

-XX:+UseG1GC

Also: -XX:+UseTLAB -XX:+ResizeTLAB  -XX:-UseBiasedLocking -XX:+AlwaysPreTouch 
but maybe those should go in a different ticket.

8GB:

op rate                   : 139805
partition rate            : 139805
row rate                  : 139805
latency mean              : 5.7
latency median            : 4.2
latency 95th percentile   : 13.2
latency 99th percentile   : 18.5
latency 99.9th percentile : 21.1
latency max               : 303.8

512MB:

op rate                   : 114214
partition rate            : 114214
row rate                  : 114214
latency mean              : 7.0
latency median            : 3.7
latency 95th percentile   : 12.4
latency 99th percentile   : 14.7
latency 99.9th percentile : 15.3
latency max               : 307.1

256MB:

op rate                   : 60028
partition rate            : 60028
row rate                  : 60028
latency mean              : 13.3
latency median            : 4.0
latency 95th percentile   : 44.7
latency 99th percentile   : 73.5
latency 99.9th percentile : 79.6
latency max               : 1105.4

Same everything with mostly stock CMS settings for 2.0. I added the  
-XX:+UseTLAB -XX:+ResizeTLAB  -XX:-UseBiasedLocking -XX:+AlwaysPreTouch 
settings to keep the numbers comparable to all of my other data.

8GB/1GB:

op rate                   : 119155
partition rate            : 119155
row rate                  : 119155
latency mean              : 6.7
latency median            : 4.1
latency 95th percentile   : 11.8
latency 99th percentile   : 15.5
latency 99.9th percentile : 17.3
latency max               : 520.2


512MB ( -XX:+UseAdaptiveSizePolicy):

op rate                   : 82375
partition rate            : 82375
row rate                  : 82375
latency mean              : 9.7
latency median            : 4.3
latency 95th percentile   : 28.2
latency 99th percentile   : 49.4
latency 99.9th percentile : 54.8
latency max               : 2642.6


256MB ( -XX:+UseAdaptiveSizePolicy):

op rate                   : 77705
partition rate            : 77705
row rate                  : 77705
latency mean              : 10.3
latency median            : 4.8
latency 95th percentile   : 33.6
latency 99th percentile   : 45.3
latency 99.9th percentile : 49.1
latency max               : 1990.0


> 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.5
>
>
> 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