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
What is the expected timeline for async benchmarks? The easy integration and advanced flamegraph-based profiling features are pretty appealing and I was looking forward to using it in an open-source project.
Hey @svix-jplatte , to_async hasn't been removed. It's behind the async feature, same as in upstream Criterion. You can enable it like this:
[dev-dependencies]
codspeed-criterion-compat = { version = "6", features = ["async_tokio"] }
# or: async_futures, async_smol, async_std
It's missing from docs.rs because docs.rs builds this crate with default features only, and those don't include async. I'll create a PR to include it, thanks for pointing this out!
Activity
art049 commentedon Jul 25, 2023
I just implemented it. I'm about to release it 😀
arindas commentedon Jul 25, 2023
Thank you so much!
svix-jplatte commentedon Nov 17, 2026
Has it been removed again? https://docs.rs/codspeed-criterion-compat/6.0.0/codspeed_criterion_compat/struct.Bencher.html doesn't show
to_async.not-matthias commentedon Nov 17, 2026
Hey @svix-jplatte ,
to_asynchasn't been removed. It's behind theasyncfeature, same as in upstream Criterion. You can enable it like this:It's missing from docs.rs because docs.rs builds this crate with default features only, and those don't include async. I'll create a PR to include it, thanks for pointing this out!