Skip to content
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

Enabled Global Lock Reservation by default on Power #12125

Merged
merged 1 commit into from
May 14, 2021

Conversation

IBMJimmyk
Copy link
Contributor

@IBMJimmyk IBMJimmyk commented Mar 4, 2021

Global Lock Reservation is now enabled by default on Power. This is the same
behavior as if the -XX:+GlobalLockReservation option was used. To use the
previous form of lock reservation, Global Lock Reservation can be disabled
with the option -XX:-GlobalLockReservation.

Global Lock Reservation is not supported on other platforms so this change
only affects Power.

Updated documentation and comments to reflect Global Lock Reservation now
being on by default on Power.

Closes: #11424
Signed-off-by: jimmyk jimmyk@ca.ibm.com

@IBMJimmyk
Copy link
Contributor Author

@zl-wang @gita-omr You might be interested in this.

@pshipton
Copy link
Member

pshipton commented Mar 4, 2021

Pls create a doc issue and PR as well.

@0xdaryl
Copy link
Contributor

0xdaryl commented Mar 5, 2021

Minor nit: please fix spelling of "Reservation" in the commit titles

@IBMJimmyk IBMJimmyk changed the title Enabled Global Lock Resrvation by default on Power Enabled Global Lock Reservation by default on Power Mar 5, 2021
@IBMJimmyk
Copy link
Contributor Author

Okay, I'll fix the commit title and open the doc issue and PR.

Copy link
Contributor

@zl-wang zl-wang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zl-wang
Copy link
Contributor

zl-wang commented Mar 5, 2021

Jenkins test sanity all jdk8,jdk11

@pshipton
Copy link
Member

pshipton commented Mar 5, 2021

Jenkins test sanity,sanity.system,extended.system,sanity.openjdk plinux,aix jdk8,jdk11

@pshipton
Copy link
Member

pshipton commented Mar 5, 2021

jenkins compile win jdk8

@pshipton
Copy link
Member

pshipton commented Mar 5, 2021

I stopped the original PR test and re-ran more testing only for plinux and AIX since these are the platforms affected. Ignore the xlinux and zlinux build failures, as they are just cancelled jobs.

@pshipton
Copy link
Member

pshipton commented Mar 5, 2021

The CheckZombieLockTest failures in AIX openjdk testing are a known issue #9186

@IBMJimmyk
Copy link
Contributor Author

Thanks for the heads up.

@pshipton
Copy link
Member

pshipton commented Mar 5, 2021

Not sure about the cmdLineTester_jvmtitests_hcr_1 failure.
Re-running in a grinder https://ci.eclipse.org/openj9/job/Grinder/1547/

@pshipton
Copy link
Member

pshipton commented Mar 5, 2021

The grinder failed 1/5.
We didn't get a jdk11 build last night, it failed due to infra. I'm creating an AIX jdk11 from the lastest and will grind that.
https://ci.eclipse.org/openj9/job/Pipeline-Build-Test-Personal/53/

@pshipton
Copy link
Member

pshipton commented Mar 6, 2021

20x grinder without this change passed https://ci.eclipse.org/openj9/job/Grinder/1548

@pshipton
Copy link
Member

pshipton commented Mar 6, 2021

Trying 20x with this change to get a better picture of the failure rate https://ci.eclipse.org/openj9/job/Grinder/1549/

@pshipton
Copy link
Member

pshipton commented Mar 6, 2021

Also 50x without the change https://ci.eclipse.org/openj9/job/Grinder/1550/

@pshipton
Copy link
Member

pshipton commented Mar 6, 2021

with change 1/20
without change 0/50

@IBMJimmyk
Copy link
Contributor Author

I'm currently taking a look to see what the problem is.

@IBMJimmyk
Copy link
Contributor Author

The grinders without the change all passed. However, with the change there were 14/100 failures. So there definitely seems to be a problem here.

@IBMJimmyk
Copy link
Contributor Author

The hanging issue in cmdLineTester_jvmtitests_hcr_1 looked to be an existing issue that was uncovered by exercising Global Lock Reservation more. The issue has since been fixed:
#12257

I rebased my changes to include the fix and reran to failing test with no problems to verify that the problem is gone.

Global Lock Reservation is now enabled by default on Power. This is the same
behavior as if the -XX:+GlobalLockReservation option was used. To use the
previous form of lock reservation, Global Lock Reservation can be disabled
with the option -XX:-GlobalLockReservation.

Global Lock Reservation is not supported on other platforms so this change
only affects Power.

Updated documentation and comments to reflect Global Lock Reservation now
being on by default on Power.

Issue: eclipse-openj9#11424
Signed-off-by: jimmyk <jimmyk@ca.ibm.com>
@zl-wang
Copy link
Contributor

zl-wang commented May 13, 2021

Jenkins test sanity,sanity.system,extended.system,sanity.openjdk plinux,aix jdk8,jdk11

@zl-wang
Copy link
Contributor

zl-wang commented May 13, 2021

@pshipton i added the comment to re-test, and it seemed tests are not initiated.

@pshipton
Copy link
Member

I see stuff running now. Sometimes it's slow, or occasionally ignored and you just need to try again after a few minutes.

@IBMJimmyk
Copy link
Contributor Author

@zl-wang zl-wang merged commit 8e6702f into eclipse-openj9:master May 14, 2021
@IBMJimmyk IBMJimmyk deleted the defaultGLR branch May 14, 2021 14:24
@doveye
Copy link
Contributor

doveye commented Jun 29, 2021

@IBMJimmyk Can you please open a docs issue/PR, as mentioned in #12125 (comment), thanks.

@IBMJimmyk
Copy link
Contributor Author

Yes, I can do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable Global Lock Reservation by Default
5 participants