[11.x] Benchmark aggregate functions #51211
Closed
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.
Purpose
Provide more insight in benchmarking results, particularly when percentiles such as p95 or min/max may have more relevance than just a typical average.
Implementation
Adds a new optional parameter to the Benchmark methods that let's you define the aggregate function(s) you want applied to the measured benchmark timings.
Adds support for ‘total’, ‘max’, ‘min’, ‘median’, percentiles via ‘pXX’, and 'all' to get all timing results.
Also allows passing an array of aggregate functions to return multiple points of data for a benchmark.
Backwards Compatibility
Default aggregate function parameter is "average" which returns the same result as this function always has. No impact to existing implementations.
Examples: