From: Adam Kalisz via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Cc: Adam Kalisz <adam.kalisz@notnullmakers.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] Chunk verification speedup discussion, similar speedup opportunities elsewhere
Date: Fri, 25 Jul 2025 13:23:57 +0200 [thread overview]
Message-ID: <mailman.116.1753442646.367.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 6313 bytes --]
From: Adam Kalisz <adam.kalisz@notnullmakers.com>
To: Proxmox Backup Server development discussion <pbs-devel@lists.proxmox.com>
Cc: Dominik Csapak <d.csapak@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Chunk verification speedup discussion, similar speedup opportunities elsewhere
Date: Fri, 25 Jul 2025 13:23:57 +0200
Message-ID: <2ac072513fdb726fd0e22fbc79425537dcf63a41.camel@notnullmakers.com>
Hi list,
I missed whether the chunk verification speedup when loading chunks got
applied or whether it was somehow included in the S3-like storage
option change set.
In
https://forum.proxmox.com/threads/abysmally-slow-restore-from-backup.133602/page-7
we have discussed some other opportunities for speedup using similar
patterns. People mentioned LXC container restore speed and host-based
backup restore, which looking at the code for the latter seems like a
similar async loop pattern would bring some improvement without too
much trouble:
https://github.com/proxmox/proxmox-backup/blob/4940514b0f05d6cd6a5f711edfdd47c1fa41b537/proxmox-backup-client/src/main.rs#L1109
Similarly the sync performance between two Proxmox Backup Servers and
live-migration got mentioned in various places.
Btw. congrats on the 4.0 beta.
Regards
Adam
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-07-25 11:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.116.1753442646.367.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=adam.kalisz@notnullmakers.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