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
8273438: Enable parallelism in vmTestbase/metaspace/stressHierarchy tests #5391
8273438: Enable parallelism in vmTestbase/metaspace/stressHierarchy tests #5391
Conversation
|
This looks like a good change to me. Please allow me some time to run multiple stress testing of these tests with exclusiveAccess removed. I should have the results tonight PST, or tomorrow. |
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.
Stability testing passed with the change. Change looks good to me.
Thank you @mseledts. I guess I need a second reviewer for this. @iignatev, @dholmes-ora? |
@shipilev 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 86 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.
|
All right, thank you! I'll integrate and see what happens next. /integrate |
Going to push as commit a143372.
Your commit was automatically rebased without conflicts. |
Current
vmTestbase/metaspace/stressHierarchy
tests (part of vmTestbase_vm_metaspace suite) contains about 15 tests, each running exclusively. There seem to be no reason to run them exclusively, though: they complete in reasonable time, are single-threaded, and consume the usual amount of memory. There is no evidence in JBS that they ever timed out without a reason, and their history unfortunately predates OpenJDK to see why they were not concurrent from day one.We should consider enabling parallelism for
vmTestbase/metaspace/stressHierarchy
and get improved test performance. Currently it is blocked byTEST.properties
withexclusiveAccess.dirs
directives in them.Note there are other exclusive tests in
vmTestbase_vm_metaspace
, but those seem to be the hard stress tests: pushing GC to the limits, or doing many threads, etc.Motivational test time improvements below.
Before:
After:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5391/head:pull/5391
$ git checkout pull/5391
Update a local copy of the PR:
$ git checkout pull/5391
$ git pull https://git.openjdk.java.net/jdk pull/5391/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5391
View PR using the GUI difftool:
$ git pr show -t 5391
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5391.diff