From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <t.lamprecht@proxmox.com> 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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E2B4D7C973 for <pbs-devel@lists.proxmox.com>; Mon, 18 Jul 2022 13:03:20 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D604D1D685 for <pbs-devel@lists.proxmox.com>; Mon, 18 Jul 2022 13:03:20 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 <pbs-devel@lists.proxmox.com>; Mon, 18 Jul 2022 13:03:19 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 40B9341DFD; Mon, 18 Jul 2022 13:03:13 +0200 (CEST) Message-ID: <15aca9fe-9c65-fa54-81db-f9440f31f4ad@proxmox.com> Date: Mon, 18 Jul 2022 13:03:12 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Thunderbird/103.0 To: Mark Schouten <mark@tuxis.nl>, Proxmox Backup Server development discussion <pbs-devel@lists.proxmox.com> References: <emf3a204a3-c161-48aa-9337-914001134e66@e231eb23.com> <b7d46762-b3bb-93af-2f8a-ad3742b7b57e@proxmox.com> <emd3a2db7f-02fe-4abf-8754-a57c0c1dfbb3@e231eb23.com> <3283c4b8-7df3-8cd8-2886-b6d14ee3633b@proxmox.com> <em6ccc3570-c17d-4163-8fab-8d65148acc39@e231eb23.com> <4a05245f-6bd1-02da-f600-9976c4f1abf5@proxmox.com> <em8c48fb27-3367-4e7f-9adf-09bac2c8390e@e231eb23.com> Content-Language: en-GB From: Thomas Lamprecht <t.lamprecht@proxmox.com> In-Reply-To: <em8c48fb27-3367-4e7f-9adf-09bac2c8390e@e231eb23.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL -0.001 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) 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 <pbs-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pbs-devel/> List-Post: <mailto:pbs-devel@lists.proxmox.com> List-Help: <mailto:pbs-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Mon, 18 Jul 2022 11:03:20 -0000 Am 18/07/2022 um 09:31 schrieb Mark Schouten: >> For one we made the libpve-storage-perl do more efficient list-snapsho= t >> requests if they can be filtered by VMID, and on the PBS side we moved= most >> operations that cause IO (and are related to backup groups/snapshots) = to a >> separate thread pool so that the main thread should be less >> congested/blocked. > Given the other responses in this thread, I=E2=80=99m not going to upgr= ade yet to a testing-version in production. Please let me know if there i= s any other info you need from me. Note that the responses where all from just one user, so not exactly a br= oad feedback, and their setup had almost no IO pressure going on, so rather a different= issue (for which we have an idea in the pipeline). 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, tha= t we suspect dea is hitting, is available in a packaged version; it'd just be interest= ing to know if the general movement of IO operations to separate threads would have h= elped in your big and (relatively) high IO pressure setup.