-
Notifications
You must be signed in to change notification settings - Fork 923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is the Score plugin ClusterAffinity necessary? #6022
Comments
While it may not be needed, it's at least useful as a Score plugin example, since there is only Filter example in the docs. |
What docs? |
On the "Customise the Scheduler" page of the docs 😅 |
If it's only intended as a Score plugin example, plugin ClusterLocality could also handle this task. |
While that's true, there is the extra NormalizeScore() function on the Affinity which could be useful for a beginner trying to understand how it works. Idk though, that's just my opinion. |
Glad you bring this up, it's a good chance to revisit all these plugins, so I created #6088 to track the effort. |
Please provide an in-depth description of the question you have:
During the scheduling process, the clusters filtered by the filter plugin will be scored by the score plugin, currently there are two score plugins
ClusterLocality
ClusterAffinity
Score plugin ClusterAffinity will give each member cluster a score of zero
ClusterAffinity also functions as a filter plugin, removing member clusters that do not meet its specified criteria. It is already effective during the filtering stage of the clustering process. However, is it necessary for ClusterAffinity to also serve as a scoring plugin to evaluate the clusters, given that it does not impact the results of the scoring phase?
What do you think about this question?:
I did a local test by propagating two workloads to the member clusters, and using the metrics collected during the scheduling process to find out how long each step took.
If keep the Score plugin ClusterAffinity
without Score plugin ClusterAffinity
While the time consumption impact of a single instance is minor, it can also save some time when there are a larger number of resources.
Environment:
The text was updated successfully, but these errors were encountered: