-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
First step of optimizing PodAffinity priority function #28952
First step of optimizing PodAffinity priority function #28952
Conversation
0f6615a
to
8c9fee5
Compare
@@ -0,0 +1,95 @@ | |||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davidopp - I splitted non_zero.go file into two parts - this is mostly copy of that with some small changes.
My only comments are suggestions for additional comments to add, so that if the next person who reads this code is as dumb as me, it will at least take them less time to understand it than it did for me. :) After you add the comments, you can apply LGTM label. Thanks! |
8c9fee5
to
a538045
Compare
Comments applied - thanks @davidopp ! |
GCE e2e build/test passed for commit a538045. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit a538045. |
Automatic merge from submit-queue |
Ref #26144
This is obviously only a first step - I will continue working on this code. However, this is changing the general scheme of computations to what is described in: #26144 (comment)