Compare benchmarks#114
Merged
curiousleo merged 4 commits intointerface-to-performancefrom Apr 29, 2020
Merged
Conversation
Owner
|
I am suprised that some of the benchmarks show a decrease in performance - am I reading this correctly? The reason I am surprised is that previous benchmarks did not show this Without Specifying RangesSpecifying RangesNow that I have looked a bit more closely I can see we weren't testing e.g. |
idontgetoutmuch
approved these changes
Apr 28, 2020
Owner
idontgetoutmuch
left a comment
There was a problem hiding this comment.
Very good tool which prompted my question but that is no reason not to merge
curiousleo
added a commit
that referenced
this pull request
May 13, 2020
curiousleo
added a commit
that referenced
this pull request
May 13, 2020
lehins
pushed a commit
that referenced
this pull request
May 18, 2020
curiousleo
added a commit
that referenced
this pull request
May 19, 2020
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
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.
The idea here is the following: in order to determine the performance impact of any change, the benchmark results need to be compared to some reference result.
bench.shjust runs the benchmarks and puts the results in a CSV file named after the current branch and commit.compare.pycompares results with a reference file and outputs any significant differences.The workflow would be to run
bench.shoninterface-to-performanceonce, then use the resulting CSV file as a reference to compare the benchmark results on feature branches against.Example output of
compare.py: