-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8315702: jcmd Thread.dump_to_file slow with millions of virtual threads #15581
Conversation
👋 Welcome back alanb! A progress list of the required criteria for merging this PR into |
@AlanBateman The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
/label remove core-libs |
@AlanBateman |
@AlanBateman |
I don't think more counts, but looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
@AlanBateman 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 17 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. ➡️ To integrate this PR with the above commit message to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me.
Thanks for reviews. |
/integrate |
Going to push as commit 3c258ac.
Your commit was automatically rebased without conflicts. |
@AlanBateman Pushed as commit 3c258ac. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk21u |
@robm-openjdk the backport was successfully created on the branch robm-openjdk-backport-3c258ac9 in my personal fork of openjdk/jdk21u. To create a pull request with this backport targeting openjdk/jdk21u:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk21u:
|
HotSpotDiagnosticMXBean.dumpThreads
andjcmd Thread.dump_to_file
are slow when there is a large number of threads.The thread dump can be sped up significantly with some small changes:
With 200k virtual threads on macOS, the plain format thread dump goes from 22s to 1.8s, and the json format thread dump goes from 31s to 2.8s on one system that I tried. On a Linux system, also with 200k threads, the plain thread dump goes from 8.7s to 2.9s, and the json format thread dump from 12.4s to 4.5s.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15581/head:pull/15581
$ git checkout pull/15581
Update a local copy of the PR:
$ git checkout pull/15581
$ git pull https://git.openjdk.org/jdk.git pull/15581/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15581
View PR using the GUI difftool:
$ git pr show -t 15581
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15581.diff
Webrev
Link to Webrev Comment