Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to Criterion for Benchmarking. #92

Closed
sfleischman105 opened this issue Mar 8, 2018 · 2 comments
Closed

Switch to Criterion for Benchmarking. #92

sfleischman105 opened this issue Mar 8, 2018 · 2 comments

Comments

@sfleischman105
Copy link
Collaborator

Right now, we use the standard libraries benchmarking tool for benchmarking.

Despite it's easy of use, there are a couple drawbacks for using it:

  • No customization on the number of runs
  • Output is limited to a number + estimated degree of confidence

It would be beneficial to switch the benchmarks to Criterion.rs, to get more detailed analysis of the benchmarks, alongside additional benchmark customization.

@sfleischman105
Copy link
Collaborator Author

May I note, this is especially important as it gives the ability to benchmark with a setup stage in-between runs, ala Bencher::iter_with_setup.

@sfleischman105
Copy link
Collaborator Author

Closed with #95

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

No branches or pull requests

1 participant