All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	"Shribman, Aidan" <aidan.shribman@sap.com>,
	qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] XBZRLE delta for live migration of large memory apps
Date: Tue, 02 Aug 2011 10:00:33 -0500	[thread overview]
Message-ID: <4E381111.5080702@codemonkey.ws> (raw)
In-Reply-To: <B5189056-4BF7-4B17-B887-AE2E803EA005@suse.de>

On 08/02/2011 09:01 AM, Alexander Graf wrote:
>
> On 02.08.2011, at 15:45, Shribman, Aidan wrote:
>
>> Subject: [PATCH v3] XBZRLE delta for live migration of large memory apps
>> From: Aidan Shribman<aidan.shribman@sap.com>
>>
>> By using XBZRLE (Xor Binary Zero Run-Length-Encoding) we can reduce VM downtime
>> and total live-migration time for VMs running memory write intensive workloads
>> typical of large enterprise applications such as SAP ERP Systems, and generally
>> speaking for representative of any application with a sparse memory update pattern.
>>
>> On the sender side XBZRLE is used as a compact delta encoding of page updates,
>> retrieving the old page content from an LRU cache (default size of 64 MB). The
>> receiving side uses the existing page content and XBZRLE to decode the new page
>> content.
>>
>> Work was originally based on research results published VEE 2011: Evaluation of
>> Delta Compression Techniques for Efficient Live Migration of Large Virtual
>> Machines by Benoit, Svard, Tordsson and Elmroth. Additionally the delta encoder
>> XBRLE was improved further using XBZRLE instead.
>>
>> XBZRLE has a sustained bandwidth of 1.5-2.2 GB/s for typical workloads making it
>> ideal for in-line, real-time encoding such as is needed for live-migration.

How does this compare to just doing gzip compression for the same workload?

Regards,

Anthony Liguori

  parent reply	other threads:[~2011-08-02 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 13:45 [Qemu-devel] [PATCH v3] XBZRLE delta for live migration of large memory apps Shribman, Aidan
2011-08-02 14:01 ` Alexander Graf
2011-08-02 14:34   ` Paolo Bonzini
2011-08-02 15:00   ` Anthony Liguori [this message]
2011-08-04  9:31     ` Shribman, Aidan
2011-08-02 18:08   ` Stefan Hajnoczi
2011-08-02 22:38   ` Avi Kivity
2011-08-02 18:05 ` Stefan Hajnoczi
2011-08-08  8:42   ` Shribman, Aidan
2011-08-08 14:02     ` Stefan Hajnoczi
2011-08-02 20:43 ` Blue Swirl
2011-08-08  8:42   ` Shribman, Aidan

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=4E381111.5080702@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=aidan.shribman@sap.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.