-
Bug
-
Resolution: Fixed
-
P4
-
21, 22
-
b15
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8316379 | 21.0.2 | Robert Mckenna | P4 | Resolved | Fixed | b02 |
HotSpotDiagnosticMXBean.dumpThreads and jcmd Thread.dump_to_file is slow when there are millions of threads.
The performance can be improved significantly if the dump of the thread info and stack trace is done with println instead of format, and the the file stream is wrapped with a buffered stream (the buffered writer used by PrintStream is not sufficient here).
Reported here:
https://mail.openjdk.org/pipermail/loom-dev/2023-September/006146.html
The performance can be improved significantly if the dump of the thread info and stack trace is done with println instead of format, and the the file stream is wrapped with a buffered stream (the buffered writer used by PrintStream is not sufficient here).
Reported here:
https://mail.openjdk.org/pipermail/loom-dev/2023-September/006146.html
- backported by
-
JDK-8316379 jcmd Thread.dump_to_file slow with millions of virtual threads
-
- Resolved
-
