Why does the ParallelGC change the Heap Size even if the Maximum Heap Size is the Same as the Minimum Heap Size?
(Doc ID 2785525.1)
Last updated on MARCH 31, 2023
Applies to:
Java SE JDK and JRE - Version 7 and laterInformation in this document applies to any platform.
Goal
According to the GC log below, the size of the heap, indicated by the number in parentheses, was changed with every GC even if the initial heap size, indicated by -XX:InitialHeapSize=3221225472 in the list of JVM options, is the same as the maximum heap size, which is specified as -XX:MaxHeapSize=3221225472.
Is this expected behavior from the Parallel garbage collector?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |