RFR: JDK-8261238: NMT should not limit baselining by size threshold [v5]

Zhengyu Gu zgu at openjdk.java.net
Wed Apr 21 11:41:44 UTC 2021


On Tue, 20 Apr 2021 05:59:54 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:

> > Would it be easier for everyone to accept this change if you introduced a runtime flag to control the threshold size, and left it at 1K by default to match the current behavior?
> > This way the default behavior does not change, but those who care can tweak it at runtime all the way to 0 to get the use case they want.
> 
> Not sure. I think the problem may be that no-one beside @zhengyu123 and me knows the code base.
> 
> @zhengyu123 what do you think, would you be more amenable toward this patch if it were guarded by an optional "-XX:+PreciseNMTButMoreMemory" switch? (Naming is facetious of course :-)

Seems no one raised concerns on memory consumption, I am good.

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

PR: https://git.openjdk.java.net/jdk/pull/2428


More information about the hotspot-runtime-dev mailing list