Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRust port of `criterion` for benchmarking #651
Comments
steveklabnik
referenced this issue
Jan 21, 2015
Closed
Rust port of `criterion` for benchmarking #6812
steveklabnik
added
the
A-wishlist
label
Jan 21, 2015
This comment has been minimized.
This comment has been minimized.
lucy
commented
May 1, 2015
|
Core_bench is also something to look at. It is broadly similar to criterion but has a possibly better way of estimating costs. |
This comment has been minimized.
This comment has been minimized.
briansmith
commented
Oct 26, 2015
|
Is this something that would affect the API, or is this purely an implementation detail? In particular, is this something that can be deferred past the stabilization of the benchmarking interface for stable Rust? |
This comment has been minimized.
This comment has been minimized.
|
criterion.rs is a thing that exists now. |
Centril
added
the
T-libs
label
Feb 23, 2018
This comment has been minimized.
This comment has been minimized.
|
Since criterion.rs exists now, I'm closing this. |
Centril
closed this
Feb 23, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
steveklabnik commentedJan 21, 2015
Wednesday May 29, 2013 at 21:22 GMT
For earlier discussion, see rust-lang/rust#6812
This issue was labelled with: A-an-interesting-project, A-benchmarks, A-instrumentation, A-libs, I-enhancement in the Rust repository
The built in unit tester presently contains some very crude one-off automated benchmarking stuff. It was initially a clone of the Go
testing.Bbenchmark system (http://golang.org/pkg/testing/#B) but started to drift towards doing statistical measurement in order to get a more stable signal.I believe Bryan O'Sullivan's
criterionlibrary (https://github.com/bos/criterion) is the state of the art here. We should port / emulate whatever it does well.