-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8274191: Improve g1 evacuation failure injector performance #5650
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
8274191: Improve g1 evacuation failure injector performance #5650
Conversation
|
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
Webrevs
|
kimbarrett
left a comment
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.
Good find. Looks good. Just a couple nits.
src/hotspot/share/gc/g1/g1YoungGCEvacFailureInjector.inline.hpp
Outdated
Show resolved
Hide resolved
|
@tschatzl 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 34 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 |
|
Thanks @albertnetymk @kimbarrett for your reviews /integrate |
|
Going to push as commit db23ecd.
Your commit was automatically rebased without conflicts. |
Hi all,
can I have reviews for this change that improves evacuation failure injector performance to be usable for pinned region performance work?
The suspected reason I think why performance is so bad (image in the CR), is that the unsynchronized reads and writes to
G1YoungGCEvacFailureInjector::_evacuation_failure_object_countcause massive performance issue if done millions of times.This change makes that counter thread-local, fixing that issue completely.
I initially had a prototype using a
THREAD_LOCAL, but when testing I had the feeling that this is/was slightly slower and I thought that adding a variable to every thread where most do not use them seems to be a waste.Testing: local testing, GHA
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5650/head:pull/5650$ git checkout pull/5650Update a local copy of the PR:
$ git checkout pull/5650$ git pull https://git.openjdk.java.net/jdk pull/5650/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5650View PR using the GUI difftool:
$ git pr show -t 5650Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5650.diff