[Cleaning Pipelines] MINOR improvements in allocation of resources #1576
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
- This commit used weights for computing the number of resources for each bucket the pipelines in buckets are sorted in order of accuracy where last buckets keeps the more performing pipelines. If initial resource value is 50 then instead of assigning 50 resources to each bucket this commit compute weight matrix and then assign the resources accordingly ensuring the last bucket gets max resource value. - Add MSVM as evaluation function - Various cleanups and seed in bandit
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.
the pipelines in buckets are sorted in order of accuracy where last buckets keeps the more
performing pipelines. If initial resource value is 50 then instead of assigning 50 resources
to each bucket this commit compute weight matrix and then assign the resources accordingly ensuring the
last bucket gets max resource value.