Avoid redundant addresses.get() in sorted numeric rangeIntoBitSet#16399
Open
sgup432 wants to merge 1 commit into
Open
Avoid redundant addresses.get() in sorted numeric rangeIntoBitSet#16399sgup432 wants to merge 1 commit into
sgup432 wants to merge 1 commit into
Conversation
Contributor
Author
|
@costin @romseygeek Do you folks mind taking a look at this? |
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
1 participant
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.
Description
While going through the doc values code where we check the value range for multi valued use-case(and cardinality is not fixed), I see we end up calling 2 decode calls for each doc like below(to calculate the number of values for a doc):
Seems redundant for consecutive documents. We can avoid one unnecessary
addresses.get()call by storing the previous offset. This is what this PR does. Simple change.