-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Rust port of criterion
for benchmarking
#6812
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
(bug triage) Good idea; not a blocker IMO. |
Visiting for triage. This would be nice, but still isn't a high-priority. |
I thought I might try to write this to help me learn Rust. I've found the testing guide and the various benchmark tests in the code. Are there any other resources I should be aware of, or design goals to keep in mind (other than emulating criterion)? I'll try to get something simple working, post it, and request feedback as I go. |
I'm tackling this issue here, I'll love to get feedback! |
Is this fixed by https://github.com/japaric/criterion.rs ? |
I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized. This issue has been moved to the RFCs repo: rust-lang/rfcs#651 |
Fix ICEs 6792 and 6793 fixes rust-lang#6792, fixes rust-lang#6793. r? `@matthiaskrgr` Fixes the ICEs by replacing `TyCtxt::type_of` with `TypeckResults::expr_ty`. changelog: none
The built in unit tester presently contains some very crude one-off automated benchmarking stuff. It was initially a clone of the Go
testing.B
benchmark 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
criterion
library (https://github.com/bos/criterion) is the state of the art here. We should port / emulate whatever it does well.The text was updated successfully, but these errors were encountered: