feat: basic bench harness #93
Open
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
Adds a basic Criterion-based benchmark harness which loads scripts from the `benches/scripts` directory and times their execution as if they were regular Rust functions. The Criterion settings were tuned for fast runs, at the expense of greater run-to-run variability. It is highly recommended that you pin the benchmark to a specific CPU core to reduce the noise.
jprochazk
force-pushed
the
basic-bench-harness
branch
from
ca5af68 to
82bc7a0
Compare
It's prohibitively slow, and it doesn't make sense to use in combination with the "faster runs" Criterion settings.
Aeledfyr
reviewed
Sep 14, 2024
Aeledfyr
reviewed
Sep 14, 2024
for real this time
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.
Adds a basic Criterion-based benchmark harness which loads scripts from the
benches/scriptsdirectory and times their execution as if they were regular Rust functions.The Criterion settings were tuned for fast runs, at the expense of greater run-to-run variability. It is highly recommended that you pin the benchmark to a specific CPU core to reduce the noise.