add optimized single and batched prefix existence APIs #14091
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.
Problem
Today, users who only need to know “does any key with this prefix exist?” typically:
This pattern incurs expensive iterator lifecycle overhead per prefix, touches many index/filter blocks with poor locality, and forces every user to reinvent the same existence check.
Solution
Introduce prefix-existence APIs that:
Performance
Note that for my workload. I do over 100K+ prefix checks per second right now, and we can definitely batch so batching is very important and optimizing this path is critical for us. I'm very open to making any other changes that will help make this path more efficient so open to suggestions.