Skip to content

Document the meaning of CPU requests & limits #50308

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

Open
tallclair opened this issue Mar 29, 2025 · 2 comments · May be fixed by #50987
Open

Document the meaning of CPU requests & limits #50308

tallclair opened this issue Mar 29, 2025 · 2 comments · May be fixed by #50987
Assignees
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tallclair
Copy link
Member

https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/ (or another page linked from there) should go into more detail on how CPU requests & limits actually work.

Specifically, on linux:

  • Requests are translated to shares (cgroups v1) or weight (cgroups v2), and a brief overview of how the linux scheduler uses those
  • Limits are translated to quota with a hardcoded period of 100ms, and a brief overview of how throttling works (in my experience, this is often misunderstood)

It would also be good to cover how windows handles these.

/sig node

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node. labels Mar 29, 2025
@lmktfy
Copy link
Contributor

lmktfy commented Apr 29, 2025

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 29, 2025
@pegasas
Copy link
Contributor

pegasas commented May 3, 2025

/assign @pegasas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants