Improve compare.py
output to use min
times and better column titles
#6134
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.
Which issue does this PR close?
Part of #6127
Rationale for this change
I want to be able to easily understand what is being compared and reported. Currently the reporting from
compare.py
is somewhat opaque:What changes are included in this PR?
min
of the iteration times to report the benchmark results -- I think this minimizes run to run variance and is the fairest way to asses performanceAre these changes tested?
No, it is a tool only change
Are there any user-facing changes?
Not really
Example output Before this PR
(note the bad headers)
Output after this PR