[
https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877432#comment-14877432
]
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: https://issues.apache.org/jira/browse/CASSANDRA-7486
> Project: Cassandra
> Issue Type: New Feature
> Components: Config
> Reporter: Jonathan Ellis
> Assignee: Benedict
> Fix For: 3.0 alpha 1
>
>
> 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)
