public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: aderumier@odiso.com
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	pve-devel <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] qemu 6 : does proxmox backup handle parallel async chunck backup like the new backup code from qemu 6.0 ?
Date: Wed, 02 Jun 2021 13:14:53 +0200	[thread overview]
Message-ID: <ee6bba57965f56a1ea42fb0a227816d63f8d6f65.camel@odiso.com> (raw)
In-Reply-To: <676f24c5-1645-f14e-8650-8b5cf1715566@proxmox.com>

Le mercredi 02 juin 2021 à 08:58 +0200, Thomas Lamprecht a écrit :
> Hi,
> 
> On 02.06.21 08:39, aderumier@odiso.com wrote:
> > I was looking for qemu 6.0 new features,
> > and it seem that they have implement parallel async chunks backup
> > (and
> > I think for other block operations, through a new block-copy
> > feature)
> > 
> > https://github.com/qemu/qemu/commit/71eed4cebed487a4f3c9f97aba83c611bbe22f8d
> > 
> > https://github.com/qemu/qemu/commit/de4641b46b020c5b332175f80e8bfe3d352888e8#diff-b33323044f2699244c126c6eae6c4083c3c99a16f4840030ac13238b1f569dc0
> > 
> > https://github.com/qemu/qemu/commit/26be9d62dd5f5268b814da24fd8e8b5c5b999ebe
> > 
> > Is it alrealy implemented or on the roadmap for the proxmox backup
> > code
> > ?
> > (To be honest, I didn't follow proxmox backup patches since a long
> > time, so I really don't known how much they are sharing with qemu
> > backup code)
> 
> the parallel stuff works with our implementation, Stefan tried it and
> with their
> default the backup is much faster, so fast that the guest cannot do
> anything during
> that anymore :D So, IIRC, Stefan turned the default number of
> parallel operations down
> for a better balance of backup speed and guest impact.
> 
ok thanks ! (I'll still don't use pbs, I'll try to test with my rbd
cluster soon to compare speed vs rbd export/import)

> FYI, we have basic packages for bullseye as base ready here, and
> possible sync to
> pvetest in the next days/weeks - in those repos there's already QEMU
> 6.0.
> 
yes, I see that.I'll try to do test soon

> Something else we can use with Bullseye/PVE 7 is io_uring instead of
> AIO, looks like
> a much saner (and actually useful) design and there should be some,
> at least slight,
> improvements due to that too.
> 
> https://kernel.dk/io_uring.pdf
> 
yes, If I remember Wolfgang had seen some bug with kernel 5.4, but I
think it's should works fine with 5.11.
I'll try it too soon :)


> cheers,
> Thomas
> 



      reply	other threads:[~2021-06-02 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  6:39 aderumier
2021-06-02  6:58 ` Thomas Lamprecht
2021-06-02 11:14   ` aderumier [this message]

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=ee6bba57965f56a1ea42fb0a227816d63f8d6f65.camel@odiso.com \
    --to=aderumier@odiso.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=pve-devel@pve.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal