[
https://issues.apache.org/jira/browse/CASSANDRA-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573099#comment-14573099
]
Matt Stump commented on CASSANDRA-8150:
---------------------------------------
We should probably close this ticket. As [~jeromatron] stated very few
optimizations with CMS appear to be generally applicable. I think the existing
defaults for tenuring threshold, survivor space, and new heap aren't good, but
rather than tune CMS I would rather use G1 as part of CASSANDRA-7486 and allow
it to self tune. Getting CMS to perform for peak throughput whilst minimizing
latency is unfortunately an application specific and iterative process.
> Revaluate Default JVM tuning parameters
> ---------------------------------------
>
> Key: CASSANDRA-8150
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8150
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Matt Stump
> Assignee: Ryan McGuire
> Attachments: upload.png
>
>
> It's been found that the old twitter recommendations of 100m per core up to
> 800m is harmful and should no longer be used.
> Instead the formula used should be 1/3 or 1/4 max heap with a max of 2G. 1/3
> or 1/4 is debatable and I'm open to suggestions. If I were to hazard a guess
> 1/3 is probably better for releases greater than 2.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
