-
Enhancement
-
Resolution: Fixed
-
P4
-
22
-
b20
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8318168 | 21.0.2 | Thomas Stuefe | P4 | Resolved | Fixed | b03 |
JDK-8318205 | 17.0.10 | Thomas Stuefe | P4 | Resolved | Fixed | b01 |
Originally, I restricted this feature to debug JVMs out of vague concerns about performance when running with NMT. However, after measuring, it turns out that the increase in cost is very small. Payoff in usefulness is huge, so I think it makes sense to have this feature always enabled. I also don't think we need a new switch for that.
- backported by
-
JDK-8318168 NMT: Make peak values available in release builds
- Resolved
-
JDK-8318205 NMT: Make peak values available in release builds
- Resolved
- relates to
-
JDK-8320061 [nmt] Multiple issues with peak accounting
- Resolved
-
JDK-8297958 NMT: Display peak values
- Resolved
- links to
-
Commit openjdk/jdk17u-dev/36372457
-
Commit openjdk/jdk21u/1deb1e2e
-
Commit openjdk/jdk/32ccf018
-
Review openjdk/jdk17u-dev/1872
-
Review openjdk/jdk21u/249
-
Review openjdk/jdk/16119