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
A common workflow with criterion (and #[bench] before that) for me is to run the benchmarks without collecting results. This is criterion's --profile-time flag, for example. Then I can run them under a profiler like perf. I scanned the blog but couldn't find anything about profiling. I see #38, but I would prefer something that just lets me run the benchmark with the harness getting out of the way as much as possible. Then I can hook it up to any profiling tool.
The text was updated successfully, but these errors were encountered:
A common workflow with criterion (and
#[bench]
before that) for me is to run the benchmarks without collecting results. This is criterion's--profile-time
flag, for example. Then I can run them under a profiler likeperf
. I scanned the blog but couldn't find anything about profiling. I see #38, but I would prefer something that just lets me run the benchmark with the harness getting out of the way as much as possible. Then I can hook it up to any profiling tool.The text was updated successfully, but these errors were encountered: