Switch benchmarks to criterion for more accurate profiling #20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While profiling the changes made in #14 and https://github.com/SenseLabsDE/contour-rs/tree/grid I noticed that I barely got any samples. After asking in the Rust Discord, this turned out to be due to the native Rust benchmarks not running for long enough.
This PR switches the benchmarks over to criterion which amongst other features runs the benchmarks for a longer time and leads to substantially better perf data. It also comes with the bonus of not requiring a nightly compiler, unlike the current benchmarks.