[
https://issues.apache.org/jira/browse/GEODE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558164#comment-17558164
]
ASF subversion and git services commented on GEODE-10385:
---------------------------------------------------------
Commit ac92c6fdabd96182a1e02a5574f1ef5faf7c2410 in geode's branch
refs/heads/develop from Dave Barnes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ac92c6fdab ]
GEODE-10385: User Guide - Remove bad G1GC tuning advice (#7815)
> User Guide: Remove bad G1 tuning advice
> ---------------------------------------
>
> Key: GEODE-10385
> URL: https://issues.apache.org/jira/browse/GEODE-10385
> Project: Geode
> Issue Type: Improvement
> Components: docs
> Affects Versions: 1.14.4
> Reporter: Dave Barnes
> Assignee: Dave Barnes
> Priority: Major
> Labels: pull-request-available
>
> The "Managing Heap Memory" page provides some G1 tuning advice that is
> actually detrimental to performance. The whole section needs some work, but
> this passage, in particular, is wrong:
> If you find the Apache Geode Resource Manager does not detect crossing the
> eviction or critical threshold quickly enough, it has been observed that its
> responsiveness is increased by reducing the default value of
> --J-XX:MaxGCPauseMillis=VALUE JVM parameter (which is 200). Be sure to take
> into account that this change also increases the amount of time spent in
> garbage collection.
> Cause: This advice was originally intended only to maximize performance of a
> specific test case. It is NOT good advice for production systems.
> https://geode.apache.org/docs/guide/114/managing/heap_use/heap_management.html
> Short-term solution: delete the passage.
> Long-term solution: Come up with some better ideas.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
