From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id AA0A01FF15E for ; Mon, 24 Nov 2025 15:17:46 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 99EE424B88; Mon, 24 Nov 2025 15:17:56 +0100 (CET) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Nicolas Frey Date: Mon, 24 Nov 2025 15:16:20 +0100 Message-ID: <176399375130.1954288.4880700490503555409.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251124110427.194887-1-n.frey@proxmox.com> References: <20251124110427.194887-1-n.frey@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1763993808679 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.147 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 KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] applied: [PATCH proxmox{, -backup} v2 0/7] tuning: verify: add verify job thread options X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" On Mon, 24 Nov 2025 12:04:20 +0100, Nicolas Frey wrote: > this patch series aims to expose configuration of the number of threads > to use for reading and verifying of verify jobs through the datastore's > tuning options. > > It expands on the series I sent last week [0], where @Thomas > suggested making this configurable through the tuning options too. > @Chris suggested adding a dedicated worker thread settings to the > datastore instead, which is an approach I don't have a problem with, > but I'd want some more opinions on. > > [...] Applied, thanks! [1/1] pbs-api-types: add default-verification-{workers, readers} to tuning options commit: 9be1e40f56224efd385d851ad1ac74070a631307 [1/6] datastore: add new thread settings to tuning options commit: 568e11a4913629f934e95e5b1f38159a2d506581 [2/6] verify: use tuning options' thread settings for {verify, read}-threads commit: 2165ea5b2023312c67728ae0d2d223ce758d6971 [3/6] ui: tuning: make default-verification-{workers, readers} configurable commit: ea62a3bc7572253427faec38911e02796d0acc0b [4/6] ui: tuning: render verification threads in tuning options commit: 23262e2bfa182bc80437665ad20865f02a5d8d94 [5/6] ui: verify: fetch default {read, verify} thread values from tuning options commit: 88d419d2cee3e91d5b1a55f2d163ded1b0591db6 [6/6] docs: tuning: document default-verification-{workers, readers} commit: a3302af5d10a7adc3fa80e228f3715672583e80e _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel