[
https://issues.apache.org/jira/browse/ARTEMIS-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607439#comment-17607439
]
ASF subversion and git services commented on ARTEMIS-3934:
----------------------------------------------------------
Commit 92964e4f001da64b1cf373e65ed0b9728d596c09 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=92964e4f00 ]
ARTEMIS-3934 restore settings equivalent to -XX:+AggressiveOpts
Before we moved to Java 11 we recommended using the -XX:+AggressiveOpts
JVM tuning option. In Java 8 this was essentially equivalent to setting
these two main parameters:
- -XX:BiasedLockingStartupDelay=500 (4000 by default)
- -XX:AutoBoxCacheMax=20000 (128 by default)
BiasedLockingStartupDelay defaults to 0 in Java 11, but AutoBoxCacheMax
still defaults to 128. Therefore, we should add
-XX:AutoBoxCacheMax=20000 to restore this optimization that's been lost
since removing -XX:+AggressiveOpts.
> Restore settings equivalent to -XX:+AggressiveOpts
> --------------------------------------------------
>
> Key: ARTEMIS-3934
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3934
> Project: ActiveMQ Artemis
> Issue Type: Task
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Before we moved to Java 11 we recommended using the {{-XX:+AggressiveOpts}}
> JVM tuning option. In Java 8 this was essentially equivalent to setting these
> two main parameters:
> - {{-XX:BiasedLockingStartupDelay=500}} ({{4000}} by default)
> - {{-XX:AutoBoxCacheMax=20000}} ({{128}} by default)
> {{BiasedLockingStartupDelay}} defaults to {{0}} in Java 11, but
> {{AutoBoxCacheMax}} still defaults to {{128}}. Therefore, we should add
> {{-XX:AutoBoxCacheMax=20000}} to restore this optimization that's been lost
> since removing {{-XX:+AggressiveOpts}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
