JDK-8314438 : NMT: Performance benchmarks are needed to have a baseline for comparison of improvements
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 22
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-08-16
  • Updated: 2025-06-13
  • Resolved: 2023-10-20
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 22
22 b21Fixed
Related Reports
Relates :  
JDK-8317453 - NMT: Performance benchmarks are needed to measure speed and memory
Description
To have a base of comparison during the NMT improvements/changes, there should be a set of performance measurements benchmarks. These performance measurements can also be used and/or received feedbacks from wider reviewers.
Comments
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/15563 Date: 2023-09-05 07:53:36 +0000
13-06-2025
Changeset: 138437f2 Author: Afshin Zafari <azafari@openjdk.org> Date: 2023-10-20 08:33:40 +0000 URL: https://git.openjdk.org/jdk/commit/138437f2cf4e965ba07212a10589a517f81623a8
20-10-2023
We should use Java Microbenchmark Harness (JMH) https://github.com/openjdk/jmh See for an example on how it can be done: https://github.com/openjdk/panama-foreign/pull/854/files
17-08-2023
The benchmark should cover the time and space measurements, i.e. how much faster/slower "our new code" is and how much less/more memory it takes.
16-08-2023