proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-06-15 19:57:33 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

pct/qm: update cpuunits default

Browse Source 
which is 100 on hosts running cgroup v2. Still mention the old default
relevant for hosts with legacy cgroups.

Also reword the sentence with "gets in regards to other VMs running"
which sounded a bit off.

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
This commit is contained in:
Fiona Ebner 2022-10-07 14:41:39 +02:00 committed by Thomas Lamprecht
parent b90b797f86
commit 48219c581f
2 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
pct.adoc
View File

@ -427,8 +427,9 @@ cpulimit: 0.5
`cpuunits`: :: This is a relative weight passed to the kernel scheduler. The `cpuunits`: :: This is a relative weight passed to the kernel scheduler. The
larger the number is, the more CPU time this container gets. Number is relative larger the number is, the more CPU time this container gets. Number is relative
to the weights of all the other running containers. The default is 1024. You to the weights of all the other running containers. The default is `100` (or
can use this setting to prioritize some containers. `1024` if the host uses legacy cgroup v1). You can use this setting to
prioritize some containers.
[[pct_memory]] [[pct_memory]]

12
qm.adoc
View File

@ -317,12 +317,12 @@ never uses more CPU time than virtual CPUs assigned set the *cpulimit* setting
to the same value as the total core count. to the same value as the total core count.
The second CPU resource limiting setting, *cpuunits* (nowadays often called CPU The second CPU resource limiting setting, *cpuunits* (nowadays often called CPU
shares or CPU weight), controls how much CPU time a VM gets in regards to other shares or CPU weight), controls how much CPU time a VM gets compared to other
VMs running. It is a relative weight which defaults to `1024`, if you increase running VMs. It is a relative weight which defaults to `100` (or `1024` if the
this for a VM it will be prioritized by the scheduler in comparison to other host uses legacy cgroup v1). If you increase this for a VM it will be
VMs with lower weight. E.g., if VM 100 has set the default 1024 and VM 200 was prioritized by the scheduler in comparison to other VMs with lower weight. E.g.,
changed to `2048`, the latter VM 200 would receive twice the CPU bandwidth than if VM 100 has set the default `100` and VM 200 was changed to `200`, the latter
the first VM 100. 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` corresponds to our `cpuunits`