Right now, the usual way to implement profiler options is to use Java system properties.
It might be much better UX for profilers to accept options more sanely, e.g.:
$ ... -jar benchmarks.jar -prof gc:detail;perfasm:events=cycles,instructions
It might be much better UX for profilers to accept options more sanely, e.g.:
$ ... -jar benchmarks.jar -prof gc:detail;perfasm:events=cycles,instructions
- relates to
-
CODETOOLS-7903142 Update WinPerfAsmProfiler documentation
-
- Resolved
-