util/interval: fix BenchmarkBTreeDeleteInsertCloneEachTime#62294
Merged
craig[bot] merged 1 commit intocockroachdb:masterfrom Mar 26, 2021
Merged
util/interval: fix BenchmarkBTreeDeleteInsertCloneEachTime#62294craig[bot] merged 1 commit intocockroachdb:masterfrom
craig[bot] merged 1 commit intocockroachdb:masterfrom
Conversation
The benchmark was not using the subtest's `b.N`, so it was getting bogus results. This confused cockroachdb#62212, which saw a regression from 0.000008611111111 nanoseconds to 0.0000101 nanoseconds. With this fix, the benchmark no longer shows any movement over the past release.
Member
35 tasks
aayushshah15
approved these changes
Mar 25, 2021
Contributor
aayushshah15
left a comment
There was a problem hiding this comment.
LGTM
Reviewable status:
complete! 0 of 0 LGTMs obtained
Contributor
Author
|
TFTR! bors r+ |
Contributor
|
Build succeeded: |
8 tasks
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 benchmark was not using the subtest's
b.N, so it was getting bogusresults. This confused #62212, which saw a regression from 0.000008611111111
nanoseconds to 0.0000101 nanoseconds.
With this fix, the benchmark no longer shows any movement over the past release
and produces much more realistic results: