Details
-
Enhancement
-
Resolution: Fixed
-
P4
-
11
-
b10
-
generic
-
generic
Description
* Why is the JIT turned off and then on again and again?
* Where has all the code heap space gone?
* Why is the method sweeper not working effectively?
Implement an on-the-fly analysis of the code heap. Trigger analysis and output via command-line parameter (state when vm shuts down) and via jcmd (at any time).
Attachments
Issue Links
- relates to
-
JDK-8200297 Build failures after JDK-8198691 (CodeHeap State Analytics)
- Closed
-
JDK-8075796 [Event Request] Add more compilation related information to JFR
- Open
-
JDK-8087107 Expose code cache statistics via perfdata counters
- Open
-
JDK-8217465 [REDO] - Optimize CodeHeap Analytics
- Resolved
-
JDK-8005885 enhance PrintCodeCache to print more data
- Resolved
-
JDK-8217250 Optimize CodeHeap Analytics
- Closed
-
JDK-8206271 CodeHeap State Analytics must digest new method state
- Resolved
-
JDK-8216314 SIGILL in CodeHeapState::print_names()
- Resolved
-
JDK-8214526 Change CodeHeap State Analytics control from UL to Print*
- Resolved
-
JDK-8306768 CodeCache Analytics reports wrong threshold
- Resolved
-
JDK-8200366 SIGSEGV in CodeHeapState::print_names()
- Closed
-
JDK-8204916 CompileBroker::print_heapinfo should redirected to log stream.
- Closed
-
JDK-8209913 Compiler output is enabled with -Xlog but doesn't use logging
- Closed
-
JDK-8200296 JTREG tests (functionality) for CodeHeap State Analytics
- In Progress
-
JDK-8316885 jcmd: Compiler.CodeHeap_Analytics cmd does not inform about missing aggregate
- Resolved