Proxmox/pve-docs
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-docs.git synced 2025-08-03 20:21:55 +03:00
Code Releases Activity

pveproxy, pvedaemon: document MAX_WORKERS setting

Browse Source 
For pveproxy, add it to the description of settings that can be
adjusted in /etc/default/pveproxy.

For pvedaemon, this is currently the only setting that can be adjusted
in /etc/default/pvedaemon.

Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
Link: https://lore.proxmox.com/20250729155227.157120-5-f.weber@proxmox.com
This commit is contained in:
Friedrich Weber
2025-07-29 17:50:58 +02:00
committed by Thomas Lamprecht
parent 0e3aaccaae
commit 7153da5a9e
2 changed files with 35 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
pvedaemon.adoc
View File

@ -30,6 +30,23 @@ NOTE: The daemon listens to a local address only, so you cannot access
it from outside. The `pveproxy` daemon exposes the API to the outside
world.
[[pvedaemon_max_workers]]
Number of Workers
-----------------
`pvedaemon` delegates handling of incoming requests to worker processes. By
default, `pvedaemon` spawns 3 worker processes, which is sufficient for most
workloads. For automation-heavy workloads that issue a huge volume of API
requests and that experience slow request handling or timeouts, the number of
worker processes can be increased by setting `MAX_WORKERS` in
`/etc/default/pvedaemon`, for example:
MAX_WORKERS=5
Note that a higher number of worker processes may result in higher CPU usage.
The number of worker processes must be greater than 0 and smaller than 128.
The same setting exists for xref:pveproxy_max_workers[pveproxy].
ifdef::manvolnum[]
include::pve-copyright.adoc[]

18
pveproxy.adoc
View File

@ -227,6 +227,24 @@ IP addresses can be specified using any syntax understood by `Net::IP`. The
name `all` is an alias for `0/0` and `::/0` (meaning all IPv4 and IPv6
addresses).
[[pveproxy_max_workers]]
Number of Workers
-----------------
`pveproxy` delegates handling of incoming requests to worker processes. By
default, `pveproxy` spawns 3 worker processes, which is sufficient for most
workloads. For automation-heavy workloads that issue a huge volume of API
requests and that experience slow request handling or timeouts, the number of
worker processes can be increased by setting `MAX_WORKERS` in
`/etc/default/pveproxy`, for example:
MAX_WORKERS=5
Note that a higher number of worker processes may result in higher CPU usage.
The number of worker processes must be greater than 0 and smaller than 128.
The same setting exists for xref:pvedaemon_max_workers[pvedaemon].
ifdef::manvolnum[]
include::pve-copyright.adoc[]
endif::manvolnum[]