From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Adam Kalisz <adam.kalisz@notnullmakers.com>, pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] Chunk verification speedup discussion, similar speedup opportunities elsewhere
Date: Fri, 25 Jul 2025 14:46:47 +0200 [thread overview]
Message-ID: <1753447301.win4nv1cia.astroid@yuna.none> (raw)
In-Reply-To: <2ac072513fdb726fd0e22fbc79425537dcf63a41.camel@notnullmakers.com>
On July 25, 2025 1:23 pm, Adam Kalisz wrote:
> 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.
https://lore.proxmox.com/pbs-devel/20250707132706.2854973-1-d.csapak@proxmox.com/
hasn't been applied (and probably needs a rebase post-S3 ;))
> 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
that's not the code path for container/host backups, that's the code
path for fixed-size indices like vm backups, but just dumping to a file
instead of via qmrestore.. i.e., nothing that is used by PVE or users
usually, but can still be improved of course ;)
> Similarly the sync performance between two Proxmox Backup Servers and
> live-migration got mentioned in various places.
do you mean live-restore here? live migration has nothing to do with
PBS..
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-07-25 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 11:23 Adam Kalisz
2025-07-25 12:46 ` Fabian Grünbichler [this message]
2025-07-28 13:14 ` Adam Kalisz
2025-07-28 13:22 ` Fabian Grünbichler
2025-08-08 13:08 ` Adam Kalisz
[not found] ` <mailman.725.1754658515.367.pve-devel@lists.proxmox.com>
2025-08-12 10:57 ` [pbs-devel] Speedups get detailed publicity Adam Kalisz
2025-07-25 15:03 ` [pbs-devel] Chunk verification speedup discussion, similar speedup opportunities elsewhere Thomas Lamprecht
2025-09-11 8:09 ` Adam Kalisz
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=1753447301.win4nv1cia.astroid@yuna.none \
--to=f.gruenbichler@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