Much faster indices lookup on metadata #123749
Merged
Conversation
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
original-brownbear added the :Data Management/Indices APIs 
nielsbauman reviewed Mar 3, 2025
server/src/main/java/org/elasticsearch/cluster/metadata/ProjectMetadata.java Outdated Show resolved Hide resolved
| Pinging @elastic/es-data-management (Team:Data Management) |
elasticsearchmachine added the Team:Data Management original-brownbear changed the title 
| This LGTM, but since I was there when we made these changes, I'd prefer if someone else had a look as well. I'll ask someone from Data Management to have a look. |
dakrone approved these changes Mar 4, 2025
original-brownbear added the auto-backport 
| Thanks you two! |
💔 Backport failed
You can use sqren/backport to manually backport by running |
georgewallace pushed a commit to georgewallace/elasticsearch that referenced this pull request Mar 11, 2025
We mostly need the map for lookups in very tight loops but also rarely rely on the sortedness of this thing. Getting the best of both worlds at surprisingly only a ~10% increase in build time and ~25% increase in the heap consumption of this structure provides a massive speedup to e.g. search or field_caps over large numbers of indices thanks to the up to an order of magnitude cheaper lookups in index name resolution and security (as well as speedups in other areas).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
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.
We mostly need the map for lookups in very tight loops but also rarely rely on the sortedness of this thing. Getting the best of both worlds at surprisingly only a ~10% increase in build time and ~25% increase in the heap consumption of this structure provides a massive speedup to e.g. search or field_caps over large numbers of indices thanks to the up to an order of magnitude cheaper lookups in index name resolution and security (as well as speedups in other areas).
Credit to @nielsbauman for finding that the tree lookups are still such a big issue and finding a solution here with me!