From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 2F84A1FF16B
	for <inbox@lore.proxmox.com>; Tue, 29 Jul 2025 21:19:22 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 6FD171BE74;
	Tue, 29 Jul 2025 21:20:47 +0200 (CEST)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Friedrich Weber <f.weber@proxmox.com>
Date: Tue, 29 Jul 2025 21:20:02 +0200
Message-ID: <175381680011.2681038.15498646118241767124.b4-ty@proxmox.com>
X-Mailer: git-send-email 2.47.2
In-Reply-To: <20250729155227.157120-2-f.weber@proxmox.com>
References: <20250729155227.157120-1-f.weber@proxmox.com>
 <20250729155227.157120-2-f.weber@proxmox.com>
MIME-Version: 1.0
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1753816805566
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.031 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: [pve-devel] applied: [PATCH http-server 1/1] api server: proxy
 config: read MAX_WORKERS integer key
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

On Tue, 29 Jul 2025 17:50:55 +0200, Friedrich Weber wrote:
> Read the MAX_WORKERS value in /etc/default/<proxyname>. If it is not
> an integer between 0 and 128, ignore and warn.
> 
> The lower limit was chosen because at least one worker process must
> exist. The upper limit was chosen because more than 127 worker
> processes should not be necessary and a positive impact on performance
> is doubtful. If this limit turns out to be too low, it can still be
> extended in the future.
> 
> [...]

Applied, thanks!

[1/1] api server: proxy config: read MAX_WORKERS integer key
      commit: d72947f112536b9ae024f48a88eb368d8209f5f9


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel