qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Orit Wasserman <owasserm@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] slow xbzrle
Date: Thu, 25 Oct 2012 11:44:20 +0200	[thread overview]
Message-ID: <508909F4.8020100@redhat.com> (raw)
In-Reply-To: <5088F46D.6080605@profihost.ag>

On 10/25/2012 10:12 AM, Stefan Priebe - Profihost AG wrote:
> Hello list,
> 
> i'm using 1.2 stable and wanted to use xbzrle but xbzrle is extremely slow.
> 
> While trying to transfer a simple VM with 4GB memory through a 10GBe nic while running a MySQL (with NO LOAD) it takes up to 10 - 15 minutes.
> 
> Remaining is often jumping or just lowering pretty slow.
This happens if the guest is dirtying his memory faster than the speed qemu is sending it.
It can happen with regular migration if the speed is too low or the downtime is too low.
> 
> Is this known or is something wrong?
My guess this workload migrates fine without XBZRLE so it is not the speed or downtime :).
it could be that the cache size is too small resulting with a lot of cache misses which means
XBZRLE makes things worse and just uses CPU to maintain the cache.
Other option is that this workload changes the pages too much which can result with a lot of over flows 
which result in XBZRLE to waste CPU scanning the pages.
As this is idle mysql my guess it the first scenario.

Can you send the cache size, cache miss and overflow (from 'info migrate')?

Thanks,
Orit
> 
> Greets,
> Stefan
> 

  reply	other threads:[~2012-10-25  9:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25  8:12 [Qemu-devel] slow xbzrle Stefan Priebe - Profihost AG
2012-10-25  9:44 ` Orit Wasserman [this message]
2012-10-25 10:35   ` Stefan Priebe - Profihost AG
2012-10-25 11:39     ` Orit Wasserman
2012-10-25 12:18       ` Stefan Priebe - Profihost AG
2012-10-25 13:15         ` Orit Wasserman
2012-10-25 20:45           ` Stefan Priebe

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=508909F4.8020100@redhat.com \
    --to=owasserm@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=s.priebe@profihost.ag \
    /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).