-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8317960: [17u] Excessive CPU usage on AbstractQueuedSynchronized.isEnqueued #1875
Conversation
👋 Welcome back alvdavi! A progress list of the required criteria for merging this PR into |
Webrevs
|
/approval |
@alvdavi usage: |
/approval request Change is present in JDK21 and considered safe. |
@alvdavi This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 115 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@phohensee) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
/sponsor |
Going to push as commit 14e6812.
Your commit was automatically rebased without conflicts. |
@phohensee @alvdavi Pushed as commit 14e6812. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This patch brings the AbstractQueuedSynchronizer related changes from JDK-8277090 to fix a performance issue that can happen in JDK17 too.
The rest of JDK-8277090 are done mostly in preparation of virtual threads and are covered under CSR JDK-8285450. There is no plan at the moment to backport the rest of the changes to 17.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1875/head:pull/1875
$ git checkout pull/1875
Update a local copy of the PR:
$ git checkout pull/1875
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1875/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1875
View PR using the GUI difftool:
$ git pr show -t 1875
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1875.diff
Webrev
Link to Webrev Comment