From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Friedrich Weber <f.weber@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager 1/2] partially fix #5392: pveproxy: make number of workers configurable
Date: Tue, 29 Jul 2025 21:19:26 +0200 [thread overview]
Message-ID: <175381676569.2680288.678897263150382475.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250729155227.157120-3-f.weber@proxmox.com>
On Tue, 29 Jul 2025 17:50:56 +0200, Friedrich Weber wrote:
> The number of pveproxy worker processes is currently hardcoded to 3.
> This may not be enough for automation-heavy workloads that trigger a
> lot of API requests that are synchronously handled by pveproxy.
>
> Hence, allow specifying MAX_WORKERS in /etc/default/pveproxy to
> override the number of workers.
>
> [...]
Applied, thanks!
[1/2] partially fix #5392: pveproxy: make number of workers configurable
commit: d7fec8f9fffc9a9405c497092da36cbc8f506bf8
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-29 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 15:50 [pve-devel] [PATCH docs/http-server/manager 0/4] fix #5392: pveproxy, pvedaemon: make number of worker processes configurable Friedrich Weber
2025-07-29 15:50 ` [pve-devel] [PATCH http-server 1/1] api server: proxy config: read MAX_WORKERS integer key Friedrich Weber
2025-07-29 19:20 ` [pve-devel] applied: " Thomas Lamprecht
2025-07-29 15:50 ` [pve-devel] [PATCH manager 1/2] partially fix #5392: pveproxy: make number of workers configurable Friedrich Weber
2025-07-29 19:19 ` Thomas Lamprecht [this message]
2025-07-29 15:50 ` [pve-devel] [PATCH manager 2/2] partially fix #5392: pvedaemon: " Friedrich Weber
2025-07-29 19:19 ` [pve-devel] applied: " Thomas Lamprecht
2025-07-29 15:50 ` [pve-devel] [PATCH docs 1/1] pveproxy, pvedaemon: document MAX_WORKERS setting Friedrich Weber
2025-07-29 19:20 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175381676569.2680288.678897263150382475.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.weber@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.