RFR: 8348278: Trim InitialRAMPercentage to improve startup in default modes [v4]

Stefan Johansson sjohanss at openjdk.org
Mon Sep 15 12:43:14 UTC 2025


On Tue, 2 Sep 2025 12:57:47 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

>> See bug for discussion. This is the code change, which is simple. What is not simple is deciding what the new value should be. The change would probably require CSR, which I can file after we agree on the value.
>> 
>> I think cutting to 0.2% of RAM size gets us into good sweet spot:
>>  - On huge 1024G machine, this yields 2G initial heap
>>  - On reasonably sized 128G machine, this gives 256M initial heap
>>  - On smaller 1G container, this gives 2M initial heap
>> 
>> Additional testing:
>>  - [x] Linux AArch64 server fastdebug, `all`
>
> Aleksey Shipilev has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains two additional commits since the last revision:
> 
>  - Also man page
>  - Fix

I started some runs in our internal perf-testing environment to see what kind of results we would get with a change like this. 

I think the reasoning sounds good for large machines, and for smaller containers some quick testing indicates that we never go below 8M for `Min/InitialHeapSize` which I also think is good. 2M sounds very small :)

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

PR Comment: https://git.openjdk.org/jdk/pull/23262#issuecomment-3291985134


More information about the hotspot-gc-dev mailing list