storage: use concrete pebbleIterator
in verifyingIterator
#86478
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.
storage: add Pebble SST iterator benchmarks
Release justification: non-production code changes
Release note: None
storage: use concrete
pebbleIterator
inverifyingIterator
Gives a slight performance boost, since it avoid dynamic dispatch:
An attempt was also made at using
RangeKeyChanged()
instead ofHasPointAndRange()
, but this had no effect.Touches #83051.
Release justification: bug fixes and low-risk updates to new functionality
Release note: None