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
8269598: Regressions up to 5% on aarch64 seems due to JDK-8268858 #4766
Conversation
|
@JoshuaZhuwj 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. |
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.
@JoshuaZhuwj This change now passes all automated pre-integration checks. 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 39 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 (@vnkozlov, @dean-long) but any other Committer may sponsor as well.
|
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.
I don't understand why aarcht64 needs these adjustments but x86 does not. Both are doing the same tricks with PreserveFramePointer, right?
Yes. If make the same adjustment on x86, the same wide LRG in But this adjustment is a trade-off in my opinion. Lowering pressure I also performed the same SPECjvm2018 "compress" test on x86_64. |
Thanks @vnkozlov @dean-long for your review. |
/integrate |
@JoshuaZhuwj |
/sponsor |
Going to push as commit 7c23491.
Your commit was automatically rebased without conflicts. |
@kelthuzadx @JoshuaZhuwj Pushed as commit 7c23491. |
@JoshuaZhuwj Please try SPECjvm2008 compress on x86/x64 with -XX:+PreserveFramePointer. We are seeing a regression after JDK-8268858. |
@dean-long Thanks for your information. Previously I already found performance degradation with -XX:+PreserveFramePointer in Alibaba Flink Nexmark benchmark. It's caused by inefficient codes generated by RA. That's why I begin working on register pressure. I already created JDK-8270808 [1] to track it. Meanwhile I will also track your mentioned regression issue together with it. Hope they're caused by the same reason. |
Just now I ran six rounds of "compress" on x64 machine with "-XX:+PreserveFramePointer". |
Hi,
Please review this change.
It fixes the SPECjvm2008 regression on aarch64 caused by JDK-8268858.
Compressor::compress() in case "compress" of SPECjvm2008 performed
degraded by 5% due to extra spillings. There existed an LRG that covered
almost the entire function, hence it interfered with more live ranges.
These interferences caused the LRG no freedom and lastly RA had to spill
it to stack. After the fix, the LRG is split into two shorter live
ranges. Both LRGs are assigned to registers due to fewer interferences.
See details at: http://cr.openjdk.java.net/~jzhu/8269598/analysis.pdf
OptoAssembly: http://cr.openjdk.java.net/~jzhu/8269598/
The root cause is:
When PreserveFramePointer is off, frame pointer is allocatable, but
different from other SOC registers, it is excluded from fatproj's mask
because its save type is No-Save. Therefore fatproj was not treated as
high-pressure transition point in the previous int_pressure_limit()
computation. This fix ensures high pressure at fatproj when
PreserveFramePointer is off. See check_pressure_at_fatproj() [1].
After this fix, the regression disappeared.
The result of regression cases in SPECjvm2008:
http://cr.openjdk.java.net/~jzhu/8269598/Book1.pdf
[1]
jdk/src/hotspot/share/opto/chaitin.hpp
Line 620 in 375fc2a
Best Regards,
Joshua
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4766/head:pull/4766
$ git checkout pull/4766
Update a local copy of the PR:
$ git checkout pull/4766
$ git pull https://git.openjdk.java.net/jdk pull/4766/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4766
View PR using the GUI difftool:
$ git pr show -t 4766
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4766.diff