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 13:39:13 +0200	[thread overview]
Message-ID: <508924E1.3@redhat.com> (raw)
In-Reply-To: <508915DE.5080509@profihost.ag>

On 10/25/2012 12:35 PM, Stefan Priebe - Profihost AG wrote:
> Am 25.10.2012 11:44, schrieb Orit Wasserman:
>>> 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')?
> 
> Example got from a log file (it's the info from info migrate just in another format):
> migration xbzrle
> cachesize: 1073741824
> transferred 0
> pages 0
> cachemiss 1315374
Looks like a lot of cache miss, you can try increasing the cache size (migrate_set_cache_size).
But you should remember that for an idle guest XBZRLE is wasteful,
it is useful for workload that changes the same memory pages frequently.

Orit 
> overflow 0
> 
> Stefan

  reply	other threads:[~2012-10-25 11:39 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
2012-10-25 10:35   ` Stefan Priebe - Profihost AG
2012-10-25 11:39     ` Orit Wasserman [this message]
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=508924E1.3@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).