From: dea <dea@corep.it>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>,
Mark Schouten <mark@tuxis.nl>
Subject: Re: [pbs-devel] Scheduler causing connectivity issues?
Date: Fri, 15 Jul 2022 14:01:28 +0200 [thread overview]
Message-ID: <de262370-49a0-3fde-890c-88131977a84d@corep.it> (raw)
In-Reply-To: <4a05245f-6bd1-02da-f600-9976c4f1abf5@proxmox.com>
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
Mmmmm no, for me the same problem.
Rollback 2.2.4 -> 2.2.1 and works great.
Il 15/07/22 13:49, Thomas Lamprecht ha scritto:
> Am 13/07/2022 um 12:41 schrieb Mark Schouten:
>> Requested files sent offlist.
> Thanks!
>
> You have 30% of runnable process getting stalled due waiting for IO, that
> naturally should not cause the request accept future to get starved but is
> the reason for why it happened with the current (or better old)
> architecture. Increasing available memory, so that the page cache can hold
> more entries, could already relieve that system a bit.
>
> We improved on the reproducer we got locally by simulating a higher latency
> disk using dm-delay on a small single core VM.
>
> 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.
>
> The results got packaged and uploaded to our test repositories and are
> available with:
>
> - proxmox-backup-server version 2.2.4-1
> - libpve-storage-perl version 7.2-7
>
> It'd be great if you could try out those and report back if they actually
> helped in your setup(s) too.
>
> cheers,
> Thomas
>
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
[-- Attachment #2.1: Type: text/html, Size: 2336 bytes --]
[-- Attachment #2.2: baySqp65HDEysz54.jpeg --]
[-- Type: image/jpeg, Size: 44243 bytes --]
next prev parent reply other threads:[~2022-07-15 12:02 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 [this message]
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
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=de262370-49a0-3fde-890c-88131977a84d@corep.it \
--to=dea@corep.it \
--cc=mark@tuxis.nl \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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