cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Shook (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7486) Migrate to G1GC by default
Date Sun, 20 Sep 2015 05:15:07 GMT


Jonathan Shook commented on CASSANDRA-7486:

I'd argue that there already is an increase in pain as you try to use more of the metal on
a node. We've just become acclimated to it. Instead of scaling the compute side over the metal,
we do silly things like run multiple instances per box. Its not really silly if it gets results,
but it is an example of where we do something tactically, get so used to it as a necessary
complexity, and then just keep taking for granted that this is how we do it. I personally
don't want to keep going down this path. So, I am inclined to carry on with the testing and
characterization, in time. We should compare notes and methods and see what can be done to
reduce the overall effort.

> Migrate to G1GC by default
> --------------------------
>                 Key: CASSANDRA-7486
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Config
>            Reporter: Jonathan Ellis
>            Assignee: Benedict
>             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