[
https://issues.apache.org/jira/browse/CASSANDRA-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229195#comment-14229195
]
Wei Deng commented on CASSANDRA-8150:
-------------------------------------
Since we're proposing to run with a much larger Eden space and
-XX:+CMSScavengeBeforeRemark, we might want to watch out if there are frequent
occurrences of "GCLocker Initiated GC" in the gc.log. According to this
discussion:
http://mail.openjdk.java.net/pipermail/hotspot-gc-dev/2014-September/010650.html,
there is a possibility for Scavenge to collide with GCLocker and makes Remark
to go longer than expected, and "GCLocker Initiated GC" can happen
unnecessarily due to this outstanding JDK bug
https://bugs.openjdk.java.net/browse/JDK-8048556.
> 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: 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)
