RFR: JDK-8297958: NMT: Display peak values [v2]

Johan Sjölen jsjolen at openjdk.org
Tue Dec 6 12:14:31 UTC 2022


On Tue, 6 Dec 2022 06:33:52 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:

> > Important addition to the memory stats in my opinion. I agree having it in release build would be great.
> > > I omit printing peak values when we are at peak. So if "peak" is missing, current peak is implied.
> > 
> > 
> > It can be confusing for others not aware of this behavior, and may think that the "peak" value is missing in the output. I believe it would be less confusing if "peak" is "always" displayed.
> 
> Thank you, @ashu-mehra!
> 
> The first version had "(peak)" written after every line if at current peak. I found the output cluttered, but let's see what others say. I'm fine with reintroducing it again.
> 
> Cheers, Thomas

If we are at peak, then instead of writing `(malloc=XKB #Y) (peak=XKB #Y)` (this is what it'd look like, right?) you can write `(malloc=XKB #Y) at peak`. It makes the peaking events visually distinct for experienced users without having to match numbers (also easy regexing) and serves as an indication to new users as to what's going on.  It  could be misinterpreted, but I think the context of a full log makes it obvious what's going on.

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

PR: https://git.openjdk.org/jdk/pull/11497


More information about the hotspot-runtime-dev mailing list