[pve-devel] [PATCH docs/http-server/manager 0/4] fix #5392: pveproxy, pvedaemon: make number of worker processes configurable
Friedrich Weber
f.weber at proxmox.com
Tue Jul 29 17:50:54 CEST 2025
>From [1]: For pveproxy and pvedaemon, max_workers is currently hardcoded to 3
in PVE::Service::{pveproxy,pvedaemon}. This may not be enough for
automation-heavy workloads that trigger a lot of API requests that are
synchronously handled by pveproxy or pvedaemon, see e.g. #5391. This was also
encountered occasionally in enterprise support.
changes since rfc:
- add limit on acceptable MAX_WORKERS setting (thx Thomas!)
- add pve-docs patch
rfc: https://lore.proxmox.com/pve-devel/20250729113523.72332-1-f.weber@proxmox.com/T/
[1] https://bugzilla.proxmox.com/show_bug.cgi?id=5392
http-server:
Friedrich Weber (1):
api server: proxy config: read MAX_WORKERS integer key
src/PVE/APIServer/Utils.pm | 8 ++++++++
1 file changed, 8 insertions(+)
manager:
Friedrich Weber (2):
partially fix #5392: pveproxy: make number of workers configurable
partially fix #5392: pvedaemon: make number of workers configurable
PVE/Service/pvedaemon.pm | 6 +++++-
PVE/Service/pveproxy.pm | 3 ++-
2 files changed, 7 insertions(+), 2 deletions(-)
docs:
Friedrich Weber (1):
pveproxy, pvedaemon: document MAX_WORKERS setting
pvedaemon.adoc | 17 +++++++++++++++++
pveproxy.adoc | 18 ++++++++++++++++++
2 files changed, 35 insertions(+)
Summary over all repositories:
5 files changed, 50 insertions(+), 2 deletions(-)
--
Generated by git-murpp 0.8.1
More information about the pve-devel
mailing list