pod-update-performance #3907
Open
pod-update-performance #3907
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
Signed-off-by: molei20021 <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
volcano-sh-bot
added
the
size/L
|
Is there a backgroup for this PR? Actually, pod will not be updated if there are no changes. |
…od-update-performance
Our
For example, one of the pod unscheduable reason is like "Pod %s/%s can possibly be assigned to %s" this may often change. |
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.
If there are thousands of pending pods in cluster, pod status update may become performance bottleneck of the whole system. I add PodStatusRateLimit config including minIntervalSec, minPodNum, enable. When the pod num of cluster is greater than minPodNum(default 10000), the times of pod status update will be limited by minIntervalSec(default 60s). If the pod unscheduleable status is updated minIntervalSec ago, we will ignore status update this time until after minIntervalSec.