kvserver/tscache: add comment to BenchmarkIntervalSklDecodeValue #160641
+4
−0
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
The `BenchmarkIntervalSklDecodeValue` benchmark was previously lacking context about how to interpret its results. This commit adds a comment explaining that the "time" variants (i.e. `sec/op`) of this benchmark can be noisy and may trigger false positives in benchmark CI issues. The allocation benchmarks are the more reliable metrics to monitor. Touches: cockroachdb#160253 Release note: None
Member
|
This change is |
arulajmani
approved these changes
Jan 7, 2026
Collaborator
Author
|
TFTR! bors r+ |
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
BenchmarkIntervalSklDecodeValuebenchmark was previously lacking context about how to interpret its results. This commit adds a comment explaining that the "time" variants (i.e.sec/op) of this benchmark can be noisy and may trigger false positives in benchmark CI issues. The allocation benchmarks are the more reliable metrics to monitor.Touches: #160253
Release note: None
Epic: None