Move per-field vector and doc-values readers from TreeMap to HashMap. #13284
Conversation
This file contains 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
Our per-field vector and doc-values readers use `TreeMap`s but don't rely on the iteration order, so these `TreeMap`s can be replaced with more CPU/RAM-efficient `HashMap`s. The per-field postings reader stays on a `TreeMap` since it relies on the iteration order.
tteofili
approved these changes
Apr 9, 2024
jpountz
added a commit
that referenced
this pull request
Apr 9, 2024
…#13284) Our per-field vector and doc-values readers use `TreeMap`s but don't rely on the iteration order, so these `TreeMap`s can be replaced with more CPU/RAM-efficient `HashMap`s. The per-field postings reader stays on a `TreeMap` since it relies on the iteration order.
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.
Our per-field vector and doc-values readers use
TreeMaps but don't rely on the iteration order, so theseTreeMaps can be replaced with more CPU/RAM-efficientHashMaps.The per-field postings reader stays on a
TreeMapsince it relies on the iteration order.