perf(610): More granular histogram buckets for timing metrics #613
Conversation
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
kulakowski
approved these changes
Nov 29, 2023
| #[name = spacetime_txn_elapsed_time_sec] | ||
| #[help = "The total elapsed (wall) time of a transaction (in seconds)"] | ||
| #[labels(txn_type: WorkloadType, db: Address, reducer: str)] | ||
| #[buckets( |
There was a problem hiding this comment.
I wouldn't mind a future refactor that has something like a
fn power_of_tens_buckets(...) -> Vec<f64> {
...
}
or something to get rid of this duplication.
Base automatically changed from
joshua/perf/607/query-cpu-time-metrics
to
master
November 29, 2023 17:27
joshua-spacetime
force-pushed
the
joshua/perf/610/granular-histogram-buckets
branch
from
17efe2b to
4ec878c
Compare
joshua-spacetime
deleted the
joshua/perf/610/granular-histogram-buckets
branch
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.
Closes #610.
Description of Changes
Please describe your change, mention any related tickets, and so on here.
API and ABI breaking changes
If this is an API or ABI breaking change, please apply the
corresponding GitHub label.
Expected complexity level and risk
How complicated do you think these changes are? Grade on a scale from 1 to 5,
where 1 is a trivial change, and 5 is a deep-reaching and complex change.
This complexity rating applies not only to the complexity apparent in the diff,
but also to its interactions with existing and future code.
If you answered more than a 2, explain what is complex about the PR,
and what other components it interacts with in potentially concerning ways.