Open
Description
@rorygraves and @mkeskells have contributed internal profiling to scalac to capture some MXBean statistics during compilation and report these broken down by compiler phase.
There is some overlap with the built-in profilers in JMH, but we can't easily replicate the ability to drill down by phase with the JMH profilers.
Can we have our cake (standardized JMH benchmark execution and statistics) and eat it too (per-phase stats)?
Possible solutions:
- Write a custom JMH profiler that reads/parses the file written by
-Yprofile
and presents them in the form understood by JMH. - Modify JMH to let the benchmarked program to trigger profiler snapshots before the phase transition, providing the phase name as an extra part of the result key.
Metadata
Metadata
Assignees
Labels
No labels