-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8341481: [perf] vframeStreamCommon constructor may be optimized #22173
Conversation
👋 Welcome back vaivanov! A progress list of the required criteria for merging this PR into |
@IvaVladimir 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 53 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 (@sspitsyn) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@IvaVladimir The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
@kimbarrett - Hi! This is the issue with copy constructors that I mentioned in the parking lot a while back. The existing code for stack walking by vFrames is allocating multiple KB for 2 temporary RegisterMap structs, and copying between them via default copy constructors. The temps are unnecessary. We believe the performance boost in SPECjbb and SPECjvm:serial are more due to not polluting the L1 cache (improving cache hit rates of other code) than the actual instruction overhead of the copy. I tried to make the RegisterMap copy constructor private so no one would use it, but there are one or two cases that still use the copy constructor that we didn't have a fix for - maybe you'll see something. Oops, I can't find the examples right off. |
For the Xeon(R) 6972P scores for the specjvm::serial for current mainline looks as: |
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.
/integrate |
@IvaVladimir |
/sponsor |
Going to push as commit 4f44cf6.
Your commit was automatically rebased without conflicts. |
@dwhite-intel @IvaVladimir Pushed as commit 4f44cf6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Optimize constructor to skip extra copy for registers. The tier1 tests are OK. The Specjvm2008 benchmark reports ~1% improvement.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22173/head:pull/22173
$ git checkout pull/22173
Update a local copy of the PR:
$ git checkout pull/22173
$ git pull https://git.openjdk.org/jdk.git pull/22173/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22173
View PR using the GUI difftool:
$ git pr show -t 22173
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22173.diff
Using Webrev
Link to Webrev Comment