P5
Oracle Solaris Studio Performance Analyzer, a Java profiler, is a highly used tool (especially internally) for performance profiling HotSpot and uses JVMTI to collect information from HotSpot.
The use case here is to be able to easily identify HotSpot VM internal threads within Performance Analyzer, (especially the TimeLine view), by the Performance Analyzer showing the HotSpot internal thread names such as we see from a HotSpot thread dump, i.e. GC task thread#0 ParallelGC, CompilerThread0, G1 Main Concurrent Mark GC Thread, Gang worker#0 (G1 Parallel Marking Threads), etc.
This information is currently not available to Performance Analyzer since there's no JVMTI event that exposes the internal HotSpot VM internal thread names.
The idea here is to improve the usability of Performance Analyzer by displaying internal HotSpot VM threads so the folks developing HotSpot can easily identify HotSpot VM threads and filter them for specific performance analysis. In a similar way, it would also make it easier for those who want to filter out internal HotSpot VM threads in the data shown in Analyzer when looking at a profile in "expert" or "machine" mode.
From talking with the Performance Analyzer team, when they have this information via JVMTI event it's trivial to add it Analyzer's display.
Hence, the RFE for a new JVMTI event to pass internal HotSpot VM thread names.
The use case here is to be able to easily identify HotSpot VM internal threads within Performance Analyzer, (especially the TimeLine view), by the Performance Analyzer showing the HotSpot internal thread names such as we see from a HotSpot thread dump, i.e. GC task thread#0 ParallelGC, CompilerThread0, G1 Main Concurrent Mark GC Thread, Gang worker#0 (G1 Parallel Marking Threads), etc.
This information is currently not available to Performance Analyzer since there's no JVMTI event that exposes the internal HotSpot VM internal thread names.
The idea here is to improve the usability of Performance Analyzer by displaying internal HotSpot VM threads so the folks developing HotSpot can easily identify HotSpot VM threads and filter them for specific performance analysis. In a similar way, it would also make it easier for those who want to filter out internal HotSpot VM threads in the data shown in Analyzer when looking at a profile in "expert" or "machine" mode.
From talking with the Performance Analyzer team, when they have this information via JVMTI event it's trivial to add it Analyzer's display.
Hence, the RFE for a new JVMTI event to pass internal HotSpot VM thread names.