cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liang Xie (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8150) Simplify and enlarge new heap calculation
Date Fri, 21 Nov 2014 03:43:35 GMT


Liang Xie commented on CASSANDRA-8150:

IMHO, the MaxTenuringThreshold setting should be different per cluster, or say, per read/write
pattern. In past, when i tuned another similar NoSQL system in our internal production clusters,
i found i need to set it to different value to get a optimized status(e.g. one cluster is
3, but another cluster is 8 or sth else)
[~tjake], totally agreed with your point! i had seen several long safepoint due to using biased
locking in Hadoop system:)

> Simplify and enlarge new heap calculation
> -----------------------------------------
>                 Key: CASSANDRA-8150
>                 URL:
>             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

View raw message