RFR: 8257901: ZGC: Take virtual memory usage into account when sizing heap [v4]

Erik Österlund eosterlund at openjdk.java.net
Thu Dec 10 10:54:36 UTC 2020


On Thu, 10 Dec 2020 09:41:49 GMT, Per Liden <pliden at openjdk.org> wrote:

>> MaxVirtMemFraction limits the amount of address space the GC should use for the heap. This is used by the heuristics in Arguments::set_heap_size() to select an appropriate default max heap size. However, that heuristic can select a max heap size that will not fit with ZGC, since ZGC uses additional address space (for multi-mapping and the virtual-to-physical ratio). As a result, if the address space is limited, and -Xmx is not specified, then ZGC might refuse to start with the error:
>> 
>> "Failed to reserve enough address space for Java heap"
>> 
>> I propose we abstract MaxVirtMemFraction to make it configurable for each GC, so that the heuristics in Arguments::set_heap_size() will pick a default max heap size that also works for ZGC.
>> 
>> Testing: Manual testing using different ulimit -v sizes.
>
> Per Liden has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Add workaround for AggressiveHeap

Marked as reviewed by eosterlund (Reviewer).

-------------

PR: https://git.openjdk.java.net/jdk/pull/1696


More information about the hotspot-dev mailing list