helix
helix copied to clipboard
Enable compute of evenness score based on a specified (prioritized) capacity key
Is your feature request related to a problem? Please describe. Currently, WAGED consider both many capacity categories/dimensions for evenness scores for the placement decision. In some use case, only one key should be relevant for evenness scores. Because, all the clusters are over-provisioned based on that category, and if evenness scores are not based on that then it introduces more movements.
Describe the solution you'd like To provide a way for users to specify a prioritized evennessScoringKey that will help computing scores based on that category only.
Additional context N/A