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/19 19:57:35 UTC
[jira] [Comment Edited] (CASSANDRA-8150) Simplify and enlarge new
heap calculation
[ https://issues.apache.org/jira/browse/CASSANDRA-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185270#comment-14185270 ]
Matt Stump edited comment on CASSANDRA-8150 at 11/19/14 6:56 PM:
-----------------------------------------------------------------
That's not quite true:
https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L75-L77
We'll use the min((100 * cores), (1/4 * max_heap))
was (Author: mstump):
That's not quite true:
https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L75-L77
We'll use the min((100 * cores), (1/4 * max_heap))
Please reopen.
> 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
>
> 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)