cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7486) Compare CMS and G1 pause times
Date Fri, 01 May 2015 18:41:10 GMT


Ariel Weisberg commented on CASSANDRA-7486:

bq. ^ G1 doesn't work that way.
I am talking about CMS. When I looked at the 12 gigabyte heap the old gen grew to 4.1 gigabytes
and I didn't see any point that it shrunk.

bq.  I'm spending all of my time tuning users' clusters where the #1 first issue every time
is getting CMS to behave.
We can make the case for G1 in different ways. If we want to do it based on real world results
that is fine with me.

To Benedict's point I think looking at all the operations we care about on realistic time
scales is something we would have to do to really know what the differences are. I wish we
had this stuff in CI so it would just be a matter of changing the flags, but we aren't there

> Compare CMS and G1 pause times
> ------------------------------
>                 Key: CASSANDRA-7486
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>          Components: Config
>            Reporter: Jonathan Ellis
>            Assignee: Shawn Kumar
>             Fix For: 2.1.x
> 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