8315437: Enable parallelism in vmTestbase/nsk/monitoring/stress/classload tests#15506
8315437: Enable parallelism in vmTestbase/nsk/monitoring/stress/classload tests#15506shipilev wants to merge 1 commit intoopenjdk:masterfrom
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
|
The fix looks okay to me but it'd be nice to find out why the |
Yeah. I cannot find a good discussion on these tests. I suspect it is mostly historical, from the times where machines were small and resource-constrained, so that a stress test made life hard for any other concurrently running test. Today, that is not the case. We have been doing e.g. GC stress tests in tier3, which can hog CPUs for minutes, without ill effects. Anyway, this is similar to other parallelism improvements we did over the previous years, e.g. https://bugs.openjdk.org/browse/JDK-8273433, https://bugs.openjdk.org/browse/JDK-8273438. Would you like to run this PR in your test systems to see if this particular relaxation is problematic? |
|
@lmesnik, may I interest you in this one too? |
|
@shipilev 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 146 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 |
|
Good, any other reviewers for this one? Thanks! |
Ping? Thanks! |
|
Thanks! /integrate |
|
Going to push as commit dd214d0.
Your commit was automatically rebased without conflicts. |
Current vmTestbase/nsk/monitoring/stress/classload tests contains 24 tests, each running exclusively. This drags the tier4 test times up. There seem to be no reason to run these tests exclusively, though: they complete in reasonable time, are lightly-threaded, and consume the usual amount of memory.
We should consider enabling parallelism for them and get improved test performance. Currently it is blocked by TEST.properties with exclusiveAccess.dirs directives in them.
Current run on 18-core machine:
2011.95s user 201.83s system 356% cpu 10:20.19 total
Fully parallel:
2274.02s user 128.64s system 2029% cpu 1:58.39 total
Additional testing:
vmTestbase/nsk/monitoring/stress/classloadProgress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15506/head:pull/15506$ git checkout pull/15506Update a local copy of the PR:
$ git checkout pull/15506$ git pull https://git.openjdk.org/jdk.git pull/15506/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15506View PR using the GUI difftool:
$ git pr show -t 15506Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15506.diff
Webrev
Link to Webrev Comment