8378176: Concurrent GC worker threads may suffer from priority inversion#30242
Open
fisk wants to merge 1 commit intoopenjdk:masterfrom
Open
8378176: Concurrent GC worker threads may suffer from priority inversion#30242fisk wants to merge 1 commit intoopenjdk:masterfrom
fisk wants to merge 1 commit intoopenjdk:masterfrom
Conversation
|
👋 Welcome back eosterlund! A progress list of the required criteria for merging this PR into |
|
❗ This change is not yet ready to be integrated. |
Contributor
Author
|
/label add hotspot-gc |
|
@fisk |
|
@fisk |
|
@fisk |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GC worker threads have elevated OS priorities, which has been found to cause priority inversion.
Increasing the priority of a thread is not something that should be done lightly. It can backfire quite a lot when facing priority inversion. Also, the thought is often that you want one set of threads in your process to be prioritized higher than another set of threads in your process. Except, priorities are global, so it becomes hard to reason about not just the priority of threads within the process, but also whether they are really more important than other threads on the system, or not.
These issues are greater with concurrent GC threads that interact not just with the other GC threads, but also with application threads. The risk for priority inversion is higher then.
Other than the difficulty of getting priorities right, elevating priorities is not possible on Linux and Mac OS, without super user privileges, which seemingly makes any potential "benefits" kind of limited to windows. Yet, running through our suite of benchmarks, no benefits have actually been sighted. Instead, I have seen priority inversion problems with ZGC.
Having concurrent worker threads have blanket high priority without inspecting everything they do with great care, is outright dangerous. This patch makes it so that concurrent GC workers have normal OS priority.
Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/30242/head:pull/30242$ git checkout pull/30242Update a local copy of the PR:
$ git checkout pull/30242$ git pull https://git.openjdk.org/jdk.git pull/30242/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 30242View PR using the GUI difftool:
$ git pr show -t 30242Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/30242.diff
Using Webrev
Link to Webrev Comment