From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C2F2E7D0C9 for ; Wed, 20 Jul 2022 09:31:22 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 86E0130F98 for ; Wed, 20 Jul 2022 09:30:52 +0200 (CEST) Received: from kerio.tuxis.nl (alrami.saas.tuxis.net [31.3.111.57]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 20 Jul 2022 09:30:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tuxis.nl; s=mail; h=from:reply-to:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=K/5u9FXw1lIsgYH6+pEwy36qhGVWgqCzY8+ZM9c0nv4=; b=XMhZUwBUb/djaiEzAq9aQGzq30rrVJNQgxHUsuvMO5SYAZ4YMsQ3kprCSOyFEQ19Z68MiTtdDQd/D 9q8FH3mOT8g7MUzf9t5/7HHP2FGh3Ynpl3snGYgTGzrtbMWuRjuWxpe50rd03qsFwNu/SaB/6+OwQd 5PYe4bPteLTOrPOymjt14WkV4deqJbCJscxlhIID2oyeYdfkFhGDZb4BNMX0hFwHWmatPMqOeZUWf0 04lTZplZH5DN6YSKj+ZARKoS3qnbpiSNtHIGMMTqgJTUoYuH2cEymozo57cSRaGYwsCx3xjFvCvIBP DyAGdCUZcwYYBGcwHEFUWhiQ+nghJGA== X-Footer: dHV4aXMubmw= Received: from [IPv6:2a03:7900:64::1000] ([2a03:7900:64::1000]) (authenticated user mark@tuxis.nl) by kerio.tuxis.nl (Kerio Connect 9.4.1 patch 1) with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Wed, 20 Jul 2022 09:30:43 +0200 From: "Mark Schouten" To: "Thomas Lamprecht" , "Proxmox Backup Server development discussion" Date: Wed, 20 Jul 2022 07:30:37 +0000 Message-Id: In-Reply-To: <15aca9fe-9c65-fa54-81db-f9440f31f4ad@proxmox.com> References: <3283c4b8-7df3-8cd8-2886-b6d14ee3633b@proxmox.com> <4a05245f-6bd1-02da-f600-9976c4f1abf5@proxmox.com> <15aca9fe-9c65-fa54-81db-f9440f31f4ad@proxmox.com> Reply-To: "Mark Schouten" User-Agent: eM_Client/9.0.1755.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.019 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pbs-devel] Scheduler causing connectivity issues? 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: , X-List-Received-Date: Wed, 20 Jul 2022 07:31:22 -0000 Hi, >FWIW, I just moved that PBS version to no-subscription, so it wouldn't be= testing >anymore. > >I'll also ping this thread once the stop gap fix for the other issue, that = we suspect >dea is hitting, is available in a packaged version; it'd just be interesti= ng to know >if the general movement of IO operations to separate threads would have he= lped in your >big and (relatively) high IO pressure setup. Upgraded to the no-subscription version and rebooting as we speak. I=E2=80= =99ll=20 keep you updated. =E2=80=94 Mark Schouten, CTO Tuxis B.V. mark@tuxis.nl