-
Enhancement
-
Resolution: Fixed
-
P4
-
11.0.13, 17, 18
-
b12
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8274014 | 17.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
JDK-8274040 | 11.0.14 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
HeapDumpAllTest.java tests the GC.heap_dump jcmd command with the "-all" flag. This triggers a heap dump without triggering a GC beforehand. This leads to the heap dump including dead objects and generally makes it larger. Since the parser used to parse the heap dump is not very fast, this makes the test run longer than the test without the "-all" flag.
SinceJDK-8267666 the test does not only create one heap dump but two. And since the second dump is created after the first one is parsed, it is much larger than the first one, containing the dead objects from the heap parsing. In my local system I get a 20 MB first dump and an 80 MB second dump. This makes the whole test runtime about 450 seconds.
Since the test only checks if the "-all" flag does not lead to errors, it would be OK to trigger a GC before the dump is triggered. This brings the runtime of the test down to 35 seconds on my machine.
Since
Since the test only checks if the "-all" flag does not lead to errors, it would be OK to trigger a GC before the dump is triggered. This brings the runtime of the test down to 35 seconds on my machine.
- backported by
-
JDK-8274014 Improve performance of HeapDumpAllTest
-
- Resolved
-
-
JDK-8274040 Improve performance of HeapDumpAllTest
-
- Resolved
-
- relates to
-
JDK-8267666 Add option to jcmd GC.heap_dump to use existing file
-
- Resolved
-
- links to
-
Commit openjdk/jdk11u-dev/78e18d45
-
Commit openjdk/jdk17u/cd1d3e01
-
Commit openjdk/jdk/73da66ff
-
Review openjdk/jdk11u-dev/337
-
Review openjdk/jdk17u/61
-
Review openjdk/jdk/5084
(4 links to)