-
Type:
Sub-task
-
Resolution: Unresolved
-
Priority:
P4
-
Affects Version/s: 26
-
Component/s: hotspot
The `AggressiveHeap` flag was originally introduced to optimize performance for specific benchmarking scenarios, but its lack of transparency and limited applicability have led to confusion and inconsistent results for general workloads. To simplify JVM configuration and encourage users to explicitly select tuning options that best fit their application needs, this flag has now been marked as deprecated and will be obsoleted and removed in future releases.
Users who wish to continue with similar behavior in the future should manually specify the corresponding flags: `-XX:+UseParallelGC -XX:+UseLargePages -XX:-ResizeTLAB -XX:TLABSize=256K -XX:YoungPLABSize=256K -XX:OldPLABSize=8K -XX:ThresholdTolerance=100` and set the following values: `-Xmx` and `-Xms` to half the available physical memory, `-XX:NewSize` to 3/8 of available physical memory, and `-XX:MaxNewSize` to the value of `-XX:NewSize`.
Users who wish to continue with similar behavior in the future should manually specify the corresponding flags: `-XX:+UseParallelGC -XX:+UseLargePages -XX:-ResizeTLAB -XX:TLABSize=256K -XX:YoungPLABSize=256K -XX:OldPLABSize=8K -XX:ThresholdTolerance=100` and set the following values: `-Xmx` and `-Xms` to half the available physical memory, `-XX:NewSize` to 3/8 of available physical memory, and `-XX:MaxNewSize` to the value of `-XX:NewSize`.