You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Async-profiler supports --jfrsync CONFIG option, see README:
--jfrsync CONFIG - start Java Flight Recording with the given configuration synchronously
with the profiler. The output .jfr file will include all regular JFR events, except that execution
samples will be obtained from async-profiler. This option implies -o jfr.
One option is, that we add it as --profile async-profiler-jfrsync option, similarly as we have --profile async-profiler-heap. And a custom configurable --async-profiler-jfrsync CONFIG where CONFIG is passed directly to --jfrsync parameter of async-profiler.
The text was updated successfully, but these errors were encountered:
Alternatively we could use --jfrsync by default. One could then configure it via --async-profiler-jfrsync CONFIG and disable it via --async-profiler-jfrsync none.
We can then also add --profile async-profiler-cpu that would measure just cpu without jfrsync, basically what does --profile async-profiler now (similar also --profile async-profiler-heap would not use jfrsync).
Async-profiler supports
--jfrsync CONFIG
option, see README:One option is, that we add it as
--profile async-profiler-jfrsync
option, similarly as we have--profile async-profiler-heap
. And a custom configurable--async-profiler-jfrsync CONFIG
whereCONFIG
is passed directly to--jfrsync
parameter of async-profiler.The text was updated successfully, but these errors were encountered: