cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Reopened] (CASSANDRA-7486) Migrate to G1GC by default
Date Sat, 19 Sep 2015 18:50:07 GMT


Benedict reopened CASSANDRA-7486:

We should revert this patch until we can do further analysis. We have significantly worse
throughput and latency figures in 3.0, and much of this can be explained by the new GC settings.
This is with more realistic workloads than we have previously benchmarked, and also with the
current state of 3.0.

[These graphs|]
paint a bleak picture. Throughput takes a 33% hit for point queries (Interestingly, there
is a reduction in GC _work_ done, presumably indicating that card marking / GC store barriers
are to blame). Latency is much worse, and much less consistent, as is throughput, for all

We may be able to use this information to counteract the problem, but releasing 3.0 GA with
this change as stands seems premature.

> Migrate to G1GC by default
> --------------------------
>                 Key: CASSANDRA-7486
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Config
>            Reporter: Jonathan Ellis
>            Assignee: Albert P Tobey
>             Fix For: 3.0 alpha 1
> See
> 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

View raw message