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 66ED31FF15C for ; Fri, 25 Jul 2025 17:02:59 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0168B1C3FE; Fri, 25 Jul 2025 17:04:18 +0200 (CEST) Message-ID: <1d041343-39be-4d90-8553-6d4fa82e4e2b@proxmox.com> Date: Fri, 25 Jul 2025 17:03:44 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Proxmox Backup Server development discussion , Adam Kalisz References: <2ac072513fdb726fd0e22fbc79425537dcf63a41.camel@notnullmakers.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <2ac072513fdb726fd0e22fbc79425537dcf63a41.camel@notnullmakers.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753455820935 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [pbs-devel] Chunk verification speedup discussion, similar speedup opportunities elsewhere X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Cc: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 25.07.25 um 13:24 schrieb Adam Kalisz: > I missed whether the chunk verification speedup when loading chunks got > applied or whether it was somehow included in the S3-like storage > option change set. btw. had a quick talk with Dominik about this topic, while having the possibility for this would be nice, server side parallelism is a different thing than client-side, as being able to starve the rest of the system of all available IO is much easier possible in the server-side case, as there is currently no knob to enforce some kind of pacing or maximum bandwidth like the bandwidth limits that client can be enforced too. So the mentioned series should IMO only be applied if it can be opted out, or, better in the long term, a pacing/IO bandwidth limit can be enforced. That is naturally a big amount of work, mostly in evaluating different options and deciding for what can make sense, that's why I mentioned that being able to opt-out could be enough, then admins could at least keep the status quo. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel