[
https://issues.apache.org/jira/browse/ARTEMIS-3934?focusedWorklogId=810555&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-810555
]
ASF GitHub Bot logged work on ARTEMIS-3934:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Sep/22 00:45
Start Date: 21/Sep/22 00:45
Worklog Time Spent: 10m
Work Description: clebertsuconic merged PR #4226:
URL: https://github.com/apache/activemq-artemis/pull/4226
Issue Time Tracking
-------------------
Worklog Id: (was: 810555)
Remaining Estimate: 0h
Time Spent: 10m
> 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)
