public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [RFC PATCH proxmox-backup stable-3 0/3] improve verify speed under certain conditions
Date: Mon,  7 Jul 2025 15:27:03 +0200	[thread overview]
Message-ID: <20250707132706.2854973-1-d.csapak@proxmox.com> (raw)

by parallelizing the chunk loading.

While talking off-list with f.gruenbichler about the pbs-restore speed
improvements, it came up that we don't parallelize the reads when
verifying snapshots.

This series introduces 2 patches that does this, the first just moves
the loading into the threads, and the second creates a seperate thread
pool just for reading.

It was developed on stable-3, if this kind of change is wanted, I would
of course send it for master too. (Some structure seems to have changed
there, so it's not a straightforward cherry-pick/port)

Dominik Csapak (3):
  verify: rename variables
  verify: move chunk loading into parallel handler
  verify: use separate read pool for reading chunks

 src/backup/verify.rs | 85 +++++++++++++++++++++++++-------------------
 1 file changed, 48 insertions(+), 37 deletions(-)

-- 
2.39.5



_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


             reply	other threads:[~2025-07-07 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 13:27 Dominik Csapak [this message]
2025-07-07 13:27 ` [pbs-devel] [RFC PATCH proxmox-backup 1/3] verify: rename variables Dominik Csapak
2025-07-07 13:27 ` [pbs-devel] [RFC PATCH proxmox-backup 2/3] verify: move chunk loading into parallel handler Dominik Csapak
2025-07-07 13:27 ` [pbs-devel] [RFC PATCH proxmox-backup 3/3] verify: use separate read pool for reading chunks Dominik Csapak

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=20250707132706.2854973-1-d.csapak@proxmox.com \
    --to=d.csapak@proxmox.com \
    --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