Github user lizhanhui commented on the issue:
    Hi @yuweitaocn , if you examine the options here carefully, you would find 
there is no "target pause time-goal", aka, RocketMQ does not set this option: 
-XX:MaxGCPauseMillis=xyz. So it's fine to set "young generation size with the 
-Xmn option".
    As a matter of fact, if you read the following section that's closely 
following the part you quoted
    > Therefore, when you evaluate the G1 GC for throughput, relax your 
pause-time target. Setting too aggressive a goal indicates that you are willing 
to bear an increase in garbage collection overhead, which has a direct impact 
on throughput. When you evaluate the G1 GC for latency, you set your desired 
(soft) real-time goal, and the G1 GC will try to meet it. As a side effect, 
throughput may suffer.
    You will find the current settings make sense.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to