public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Mark Schouten <mark@tuxis.nl>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Scheduler causing connectivity issues?
Date: Mon, 18 Jul 2022 13:03:12 +0200	[thread overview]
Message-ID: <15aca9fe-9c65-fa54-81db-f9440f31f4ad@proxmox.com> (raw)
In-Reply-To: <em8c48fb27-3367-4e7f-9adf-09bac2c8390e@e231eb23.com>

Am 18/07/2022 um 09:31 schrieb Mark Schouten:

>> For one we made the libpve-storage-perl do more efficient list-snapshot
>> 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’m not going to upgrade yet to a testing-version in production. Please let me know if there is any other info you need from me.

Note that the responses where all from just one user, so not exactly a broad 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, that we suspect
dea is hitting, is available in a packaged version; it'd just be interesting to know
if the general movement of IO operations to separate threads would have helped in your
big and (relatively) high IO pressure setup.




  reply	other threads:[~2022-07-18 11:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 15:49 Mark Schouten
2022-07-08  7:09 ` Thomas Lamprecht
2022-07-08  9:36   ` Jorge Boncompte
2022-07-08  9:40     ` dea
2022-07-11  8:44   ` Mark Schouten
2022-07-13  7:55     ` dea
2022-07-13  8:14     ` Thomas Lamprecht
2022-07-13 10:41       ` Mark Schouten
2022-07-15 11:49         ` Thomas Lamprecht
2022-07-15 12:01           ` dea
2022-07-15 12:57             ` Thomas Lamprecht
2022-07-15 13:02               ` dea
2022-07-15 13:24                 ` dea
2022-07-15 14:43                   ` dea
2022-07-17 15:04                   ` dea
2022-07-18 13:30                     ` Thomas Lamprecht
2022-07-19 11:01                       ` David Lawley
2022-07-19 13:04                         ` Thomas Lamprecht
2022-07-19 15:08                           ` dea
2022-07-18  7:31           ` Mark Schouten
2022-07-18 11:03             ` Thomas Lamprecht [this message]
2022-07-20  7:30               ` Mark Schouten
2022-07-21 13:10                 ` Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15aca9fe-9c65-fa54-81db-f9440f31f4ad@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=mark@tuxis.nl \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal