CODETOOLS-7903484: JMH: Use ThreadMXBean.getTotalThreadAllocatedBytes for -prof gc #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JDK 21 comes with a new method that gives the total allocated rate for all the threads, JDK-8304074. JMH -prof gc can use it, when available. This allows catching the totality of the thread allocations, regardless whether the threads went in or out during the lifetime of the benchmark. Current
-prof gcis missing those threads most of the time.Example benchmark:
Current JDK 20:
Self-built JDK 21-ea:
Note: GHA testing would not be clean until
21-earelease catches up and contains JDK-8304074.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jmh.git pull/106/head:pull/106$ git checkout pull/106Update a local copy of the PR:
$ git checkout pull/106$ git pull https://git.openjdk.org/jmh.git pull/106/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 106View PR using the GUI difftool:
$ git pr show -t 106Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jmh/pull/106.diff
Webrev
Link to Webrev Comment