-
Type:
Sub-task
-
Resolution: Unresolved
-
Priority:
P4
-
Affects Version/s: 26
-
Component/s: hotspot
To simplify ergonomic heap sizing and reduce user confusion, the `MaxRAM flag has been marked as deprecated and will be obsoleted and removed in future releases. Explicit configuration of `MaxRAM` is rarely necessary, as the JVM accurately detects available physical memory and system commit limits. Setting `MaxRAM` above the actual physical memory may lead to misconfiguration or incorrect sizing, and is not a common use case.
Additionally, the default value of `MaxRAM` has been removed. From now on and until the `MaxRAM` flag is obsoleted, all memory calculations are based on the available memory on the system rather than the default value of `MaxRAM`, unless `MaxRAM` is explicitly set by the user.
Users who need to control the heap size directly are encouraged to use standard, well-supported flags such as `-Xms` and `-Xmx` instead.
Additionally, the default value of `MaxRAM` has been removed. From now on and until the `MaxRAM` flag is obsoleted, all memory calculations are based on the available memory on the system rather than the default value of `MaxRAM`, unless `MaxRAM` is explicitly set by the user.
Users who need to control the heap size directly are encouraged to use standard, well-supported flags such as `-Xms` and `-Xmx` instead.