Add benchmark option to tests #63
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
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.
to help with performance testing this PR adds opt-in benchmarks to tests. They are disabled by default, but use
pytest --benchmark-enable(ortox -e benchmark) to get performance metrics. They will be saved to your local.benchmarkdirectory (I stopped short of setting this up to save results on CI), so you can checkout various commits and see how they compare. by default it compares to the last run, but you can use (for example)pytest-benchmark compare 0001 0005to compare test 0001 to test 0005 from your .benchmarks folder