Speed up DataTierAllocationDecider (#78075)#78167
Merged
original-brownbear merged 1 commit intoelastic:7.xfrom Sep 22, 2021
original-brownbear:78075-7.x
Merged
Speed up DataTierAllocationDecider (#78075)#78167original-brownbear merged 1 commit intoelastic:7.xfrom original-brownbear:78075-7.x
original-brownbear merged 1 commit intoelastic:7.xfrom
original-brownbear:78075-7.x
Conversation
This decider is quite slow in `allocationAllowed` and shows up in profiling. We should be able to get a much tighter loop with this change that avoids building the list of role names over and over and removes some dead code as well. Co-authored-by: Joe Gallo <joegallo@gmail.com>
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
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
3 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.
This decider is quite slow in
allocationAllowedand shows up in profiling.We should be able to get a much tighter loop with this change that avoids building
the list of role names over and over and removes some dead code as well.
Co-authored-by: Joe Gallo joegallo@gmail.com
backport of #78075