proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-04 15:55:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

qm: resource limits: revise section cpuunits

Browse Source 
* restructure sentences minimally
* improve section-formatting

Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
This commit is contained in:
Alexander Zeidler 2024-01-16 14:22:39 +01:00 committed by Thomas Lamprecht
parent d17b6bd3d5
commit 6a31c01b5a
1 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
qm.adoc
View File

@ -364,17 +364,21 @@ up to use more CPU time than just its virtual CPUs could use. To ensure that a
VM never uses more CPU time than vCPUs assigned, set the *cpulimit* to VM never uses more CPU time than vCPUs assigned, set the *cpulimit* to
the same value as the total core count. the same value as the total core count.
The second CPU resource limiting setting, *cpuunits* (nowadays often called CPU *cpuuntis*
shares or CPU weight), controls how much CPU time a VM gets compared to other
running VMs. It is a relative weight which defaults to `100` (or `1024` if the With the *cpuunits* option, nowadays often called CPU shares or CPU weight, you
host uses legacy cgroup v1). If you increase this for a VM it will be can control how much CPU time a VM gets compared to other running VMs. It is a
prioritized by the scheduler in comparison to other VMs with lower weight. For relative weight which defaults to `100` (or `1024` if the host uses legacy
example, if VM 100 has set the default `100` and VM 200 was changed to `200`, cgroup v1). If you increase this for a VM it will be prioritized by the
the latter VM 200 would receive twice the CPU bandwidth than the first VM 100. scheduler in comparison to other VMs with lower weight.
For example, if VM 100 has set the default `100` and VM 200 was changed to
`200`, the latter VM 200 would receive twice the CPU bandwidth than the first
VM 100.
For more information see `man systemd.resource-control`, here `CPUQuota` For more information see `man systemd.resource-control`, here `CPUQuota`
corresponds to `cpulimit` and `CPUWeight` corresponds to our `cpuunits` corresponds to `cpulimit` and `CPUWeight` to our `cpuunits` setting. Visit its
setting, visit its Notes section for references and implementation details. Notes section for references and implementation details.
The third CPU resource limiting setting, *affinity*, controls what host cores The third CPU resource limiting setting, *affinity*, controls what host cores
the virtual machine will be permitted to execute on. E.g., if an affinity value the virtual machine will be permitted to execute on. E.g., if an affinity value