From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Adam Kalisz <adam.kalisz@notnullmakers.com>, pbs-devel@lists.proxmox.com
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [pbs-devel] Chunk verification speedup discussion, similar speedup opportunities elsewhere
Date: Mon, 28 Jul 2025 15:22:33 +0200 [thread overview]
Message-ID: <1753708847.wueupzjnbf.astroid@yuna.none> (raw)
In-Reply-To: <874cbfc3d659edb7c8ebdda71e77530e437065a2.camel@notnullmakers.com>
On July 28, 2025 3:14 pm, Adam Kalisz wrote:
> On Fri, 2025-07-25 at 14:46 +0200, Fabian Grünbichler wrote:
>> On July 25, 2025 1:23 pm, Adam Kalisz wrote:
>> > 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..
>
> I threw more things into a single basked as the e-mail was sent to both
> lists and meant live migration that seems like it could go faster in
> some cases. (But that might be code that originates in the QEMU
> project, right?) We could of course have a look at live-restore or even
> some things like migration from VMware/ ESXi too (again, unrelated to
> PBS).
yes, live migration also has some performance optimizations that we want
to check out, in particular the multi-FD feature:
https://bugzilla.proxmox.com/show_bug.cgi?id=5766
live restore uses an entirely different mechanism, and migration from
ESXi uses yet another mechanism that is bottle-necked by the API on the
other side at the moment.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-28 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ac072513fdb726fd0e22fbc79425537dcf63a41.camel@notnullmakers.com>
2025-07-25 15:03 ` Thomas Lamprecht
[not found] ` <1753447301.win4nv1cia.astroid@yuna.none>
2025-07-28 13:14 ` Adam Kalisz via pve-devel
[not found] ` <874cbfc3d659edb7c8ebdda71e77530e437065a2.camel@notnullmakers.com>
2025-07-28 13:22 ` Fabian Grünbichler [this message]
2025-08-08 13:08 ` Adam Kalisz via pve-devel
2025-08-12 10:57 ` [pve-devel] Speedups get detailed publicity Adam Kalisz via pve-devel
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=1753708847.wueupzjnbf.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=adam.kalisz@notnullmakers.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-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