From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Orit Wasserman <owasserm@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] migration: use XBZRLE only after bulk stage
Date: Fri, 01 Mar 2013 07:08:55 -0700 [thread overview]
Message-ID: <5130B677.1060604@redhat.com> (raw)
In-Reply-To: <5130B5D8.7030308@dlhnet.de>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On 03/01/2013 07:06 AM, Peter Lieven wrote:
>> Do you have any benchmark numbers? At any rate, the explanation seems
>> sound, so a benchmark should show this.
>
> Do you have a particular test pattern in mind? If there is nothing going on
> in the VM XBZRLE will not be better than normal copy at all.
>
> Otherwise you will have N xbzrle misses and 0 xbzrle pages without the
> patch
> and 0 xbzrle misses and 0 xbzrle pages with the patch.
How about a migration of a guest running the synthetic r/w load
generator in docs/xbzrle.txt?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-03-01 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 13:31 [Qemu-devel] [PATCH] migration: use XBZRLE only after bulk stage Peter Lieven
2013-03-01 13:52 ` Eric Blake
2013-03-01 13:53 ` Paolo Bonzini
2013-03-01 14:06 ` Peter Lieven
2013-03-01 14:08 ` Eric Blake [this message]
2013-03-01 14:13 ` Peter Lieven
2013-03-01 14:23 ` Eric Blake
2013-03-01 14:50 ` Peter Lieven
2013-03-01 16:04 ` Eric Blake
2013-03-04 17:10 ` Peter Lieven
2013-03-04 17:33 ` Paolo Bonzini
2013-03-04 17:39 ` Peter Lieven
2013-03-04 18:51 ` Orit Wasserman
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=5130B677.1060604@redhat.com \
--to=eblake@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@dlhnet.de \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).