You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2022/09/21 16:00:00 UTC
[jira] [Closed] (ARTEMIS-3934) Restore settings equivalent to -XX:+AggressiveOpts
[ https://issues.apache.org/jira/browse/ARTEMIS-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clebert Suconic closed ARTEMIS-3934.
------------------------------------
Fix Version/s: 2.26.0
Resolution: Fixed
> 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
> Fix For: 2.26.0
>
> 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)