-
Type:
Sub-task
-
Resolution: Delivered
-
Priority:
P4
-
Affects Version/s: 26
-
Component/s: hotspot
To simplify heap sizing and reduce user confusion, the `MaxRAM` flag has been marked as deprecated with the intent to 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 incorrect heap 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, heap sizing 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 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, heap sizing 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 flags such as `-Xms` and `-Xmx` instead.