8350285: Shenandoah: Regression caused by ShenandoahLock under extreme contention #3614
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.
Backport for ShenandoahLock performance regression issue. The fix involves sleeping for a very short duration every 3 yields, with the number of yields picked through manual testing.
Clean backport, ran GHA sanity checks and locally tested
tier1
,tier2
, andhotspot_gc_shenandoah
.test/jdk/java/nio/channels/FileChannel/directio/DirectIOTest.java
sometimes fails locally, but it also sometimes failed before the fix.Progress
Error
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/3614/head:pull/3614
$ git checkout pull/3614
Update a local copy of the PR:
$ git checkout pull/3614
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/3614/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3614
View PR using the GUI difftool:
$ git pr show -t 3614
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/3614.diff