JDK-8366690 : Release Note: Default initial heap size is trimmed down
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 26
  • Priority: P4
  • Status: Resolved
  • Resolution: Delivered
  • Submitted: 2025-09-02
  • Updated: 2025-09-22
  • Resolved: 2025-09-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 26
26Resolved
Description
When user does not specify `-Xms`, JVM ergonomics guesses the initial heap size, based on `InitialRAMPercentage` setting, currently set at 1/64 of physical RAM. The initial heap size drives the startup times, because GCs need to initialize their internal data structures, e.g. remsets, card tables, or even heap memory itself for the initial heap. This heuristics had not changed for decades, and modern computers ship with much larger system memories, which initializes a very large initial heap. 

This release trims `InitialRAMPercentage` to `0.2`, improving the startup time for default JVM modes. In case this change causes any problems, users are advised to either specify more reasonable `Xms` explicitly, or override the `InitialRAMPercentage` setting.