-
Notifications
You must be signed in to change notification settings - Fork 43k
Kubelet CPU perf regression 1.20->1.21 (10-15%) #101989
Copy link
Copy link
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/regressionCategorizes issue or PR as related to a regression from a prior release.Categorizes issue or PR as related to a regression from a prior release.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Milestone
Description
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/regressionCategorizes issue or PR as related to a regression from a prior release.Categorizes issue or PR as related to a regression from a prior release.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Type
Projects
Status
Done
/cc @ehashman
/cc @bobbypage
What happened:
1.21 kubelet shows perf degradation on our tests. Also here https://bugzilla.redhat.com/show_bug.cgi?id=1953102.
The root cause seems to be runc, should be fixed here: #101888.
This issue is to discuss backporting of the fix to 1.21 release.
What you expected to happen:
Kubelet doesn't show significant change in CPU between 1.20 and 1.21.
How to reproduce it (as minimally and precisely as possible):
No special set up required. Just perf observation.
Anything else we need to know?:
Environment:
kubectl version): 1.21