Add benchmark entrypoint and noxfile target #31
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.
This adds a benchmark suite based on the samples demo using
pyperf. It will write files to the ./benchmark_result directory (gitignored) and you can usepyperfto compare results between multiple runs.At the moment the complete benchmark runs very slowly (hours). You can run the benchmark against a subset of the sample files by naming which ones to include on the command line, which is much faster as only a couple of the sample files are slow.
In the future I would like to have open PRs run benchmarks in CI and have CI automation add a comment to the PR if performance is significantly degraded by the PR.