RFR: 8186248 - Allow more flexibility in selecting Heap % of available RAM
David Holmes
david.holmes at oracle.com
Tue Aug 29 06:51:34 UTC 2017
Hi Bob,
This looks good - thanks.
Just to clarify the behaviour - the new percentage flag wins if both new
and old flags are specified (and of course use of the old flag gets a
deprecation warning).
I'm a little surprised these flags don't need special treatment in
TestOptionsWithRanges - but if the fraction forms didn't need it then
the percentage forms should not either.
Once the CSR request is updated and approved this can be finalized.
Thanks,
David
On 29/08/2017 12:40 AM, Bob Vandette wrote:
> Please review this updated webrev with changes suggested by David Holmes.
>
> Webrev:
>
> http://cr.openjdk.java.net/~bobv/8186248/webrev.02 <http://cr.openjdk.java.net/~bobv/8186248/webrev.02>
>
> This CR https://bugs.openjdk.java.net/browse/JDK-8186248 <https://bugs.openjdk.java.net/browse/JDK-8186248> deprecates
> the MaxRAMFraction, MinRAMFraction and InitialRAMFraction VM options
> in JDK 10 and adds three new options which allow the user the ability to
> select a percentage of available memory to be used for the Java Heap.
>
> MaxRAMPercentage
> MinRAMPercentage
> InitialRMAPercentage
>
> Please let me know if anyone objects to the flag name and deprecation as I am in
> the process of filing a CCC (CSR).
>
> Thanks,
> Bob.
>
>
>
>
>
>
More information about the hotspot-dev
mailing list