You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When pods are scheduled and started with static CPU binding policy and Linux cpuset controller, we expect that the pod/containers can use all the cpuset CPUs and not get throttled by Linux CFS Bandwidth Control. However, there are results which pods still have chance to get cfs throttled if cpu.cfs_quota_us is set (according to container's CPU limit).
What happened:
When pods are scheduled and started with static CPU binding policy and Linux cpuset controller, we expect that the pod/containers can use all the cpuset CPUs and not get throttled by Linux CFS Bandwidth Control. However, there are results which pods still have chance to get cfs throttled if
cpu.cfs_quota_us
is set (according to container's CPU limit).e.g.
Pod A:
What you expected to happen:
cpuset pods should not have cfs throttles. We may disable
cpu.cfs_quota_us
for the cpuset pods via the koordlet.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): 1.22FYI:
The text was updated successfully, but these errors were encountered: