>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.Marking as RFC, as - I'm not sure if the feature is a good idea and the implementation is acceptable - Documentation is currently missing. If this RFC is deemed acceptable, I'd include it in the v1. [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 | 7 +++++++ 1 file changed, 7 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(-) Summary over all repositories: 3 files changed, 14 insertions(+), 2 deletions(-) -- Generated by git-murpp 0.8.1 _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
