feat: add benchmark repetition #27
Merged
Conversation
This file contains 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
RafaelGSS
requested changes
Dec 10, 2024
|
Could you also update the docs? |
|
Sure @RafaelGSS , I believe makes sense, I gonna update the docs and rename it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello there, this is related to this issue #6.
This PR aims to introduce benchmark repetition as an optional parameter. By running benchmarks multiple times and averaging the results, we can minimize noise and improve the accuracy of the measurements.
Below, you’ll find a comparison of benchmarks with repetition versus those without:
Let me know if need add something, thanks :)