You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matt Stump (JIRA)" <ji...@apache.org> on 2014/11/20 23:52:34 UTC
[jira] [Updated] (CASSANDRA-8150) Simplify and enlarge new heap
calculation
[ https://issues.apache.org/jira/browse/CASSANDRA-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Stump updated CASSANDRA-8150:
----------------------------------
Attachment: upload.png
Just to emphasize the point I just got word of another unrelated customer that rolled out the changes. Here is a graph of their GC activity. Additionally, write latency was cut in half.
> Simplify and enlarge new heap calculation
> -----------------------------------------
>
> Key: CASSANDRA-8150
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8150
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Matt Stump
> Assignee: Brandon Williams
> 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)