-
Sub-task
-
Resolution: Delivered
-
P4
-
21.0.2, 22
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8324558 | 21.0.2 | Marc Palmerjohnson | P4 | Resolved | Delivered | |
JDK-8324552 | 17.0.10 | Marc Palmerjohnson | P4 | Closed | Withdrawn |
NMT reports will now show peak values for all categories. Peak values contain the highest value for committed memory in a given NMT category over the lifetime of the JVM process.
If the committed memory for an NMT category is currently at peak, NMT prints "at peak"; otherwise, it prints the peak value.
For example:
```
- Compiler (reserved=230KB, committed=230KB)
(malloc=34KB #64) (peak=49KB #71)
(arena=196KB #4) (peak=6126KB #16)
```
This shows Compiler arena memory peaked at a bit more than 6MB, whereas it now hovers around 200 KB.
If the committed memory for an NMT category is currently at peak, NMT prints "at peak"; otherwise, it prints the peak value.
For example:
```
- Compiler (reserved=230KB, committed=230KB)
(malloc=34KB #64) (peak=49KB #71)
(arena=196KB #4) (peak=6126KB #16)
```
This shows Compiler arena memory peaked at a bit more than 6MB, whereas it now hovers around 200 KB.
- backported by
-
JDK-8324558 Release Note: NMT: Make Peak Values Available in Release Builds
-
- Resolved
-
-
JDK-8324552 Release Note: NMT: Make Peak Values Available in Release Builds
-
- Closed
-