-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 17, 21, 22
-
b15
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8319223 | 21.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b05 |
JDK-8334833 | 17.0.13 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
Current vmTestbase/gc/g1/unloading tests contain 112 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 16-core machine:
4340.46s user 107.99s system 128% cpu 57:37.79 total
Fully parallel:
4138.37s user 84.50s system 808% cpu 8:42.62 total
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 16-core machine:
4340.46s user 107.99s system 128% cpu 57:37.79 total
Fully parallel:
4138.37s user 84.50s system 808% cpu 8:42.62 total
- backported by
-
JDK-8319223 Enable parallelism in vmTestbase/gc/g1/unloading tests
-
- Resolved
-
-
JDK-8334833 Enable parallelism in vmTestbase/gc/g1/unloading tests
-
- Resolved
-
- links to
-
Commit openjdk/jdk17u-dev/02ec672c
-
Commit openjdk/jdk21u/3e46e29d
-
Commit openjdk/jdk/825e0ed2
-
Review openjdk/jdk17u-dev/2607
-
Review openjdk/jdk21u/296
-
Review openjdk/jdk/15598
(3 links to)