Skip to content

re: timeline on async benchmarks #6

Closed

Description

@arindas

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.

Activity

  1. art049 commented on Jul 25, 2023

    @art049
    Member

    I just implemented it. I'm about to release it 😀

  2. arindas commented on Jul 25, 2023

    @arindas
    Author

    Thank you so much!

  3. svix-jplatte commented on Nov 17, 2026

    @svix-jplatte
  4. not-matthias commented on Nov 17, 2026

    @not-matthias
    Member

    Has it been removed again? docs.rs/codspeed-criterion-compat/6.0.0/codspeed_criterion_compat/struct.Bencher.html doesn't show to_async.

    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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions