qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Chegu Vinod <chegu_vinod@hp.com>
Cc: pbonzini@redhat.com, owasserm@redhat.com, qemu-devel@nongnu.org,
	anthony@codemonkey.ws, quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v2] Throttle-down guest when live migration does not converge.
Date: Mon, 29 Apr 2013 08:53:45 -0600	[thread overview]
Message-ID: <517E8979.6090103@redhat.com> (raw)
In-Reply-To: <1367095836-19318-1-git-send-email-chegu_vinod@hp.com>

[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]

On 04/27/2013 02:50 PM, Chegu Vinod wrote:
> Busy enterprise workloads hosted on large sized VM's tend to dirty
> memory faster than the transfer rate achieved via live guest migration.
> Despite some good recent improvements (& using dedicated 10Gig NICs
> between hosts) the live migration does NOT converge.
> 

> 
> No exernal trigger is required (unlike option 1) and it can co-exist

s/exernal/external/

> with enhancements being pursued as part of Option 2 (e.g. RDMA).
> 
> Thanks to Juan and Paolo for their useful suggestions.
> 

> 
> ---
> 
> (qemu) info migrate
> capabilities: xbzrle: off auto-converge: on   <----

This part looks nice.

I'm not reviewing the entire patch (I'm not an expert on the internals
of migration), but just the interface:

> +++ b/qapi-schema.json
> @@ -599,10 +599,14 @@
>  #          This feature allows us to minimize migration traffic for certain work
>  #          loads, by sending compressed difference of the pages
>  #
> +# @auto-converge: Controls whether or not the we want the migration to
> +#          automaticially detect and force convergence by slowing

s/automaticially/automatically/

> +#          down the guest. Disabled by default.

Missing a (since 1.6) designation.

Also, use of first-person (us, we) in docs seems a bit unprofessional,
although you were copying pre-existing usage.  How about:

@xbzrle: Migration supports xbzrle (Xor Based Zero Run Length Encoding),
         which minimizes migration traffic for certain workloads by
         sending compressed differences of active pages

@auto-converge: Migration supports automatic throttling of guest
                activity to force convergence (since 1.6)

-- 
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 --]

  reply	other threads:[~2013-04-29 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27 20:50 [Qemu-devel] [RFC PATCH v2] Throttle-down guest when live migration does not converge Chegu Vinod
2013-04-29 14:53 ` Eric Blake [this message]
2013-04-29 17:48   ` Chegu Vinod
2013-04-30 15:04 ` Orit Wasserman
2013-04-30 17:51   ` Chegu Vinod
2013-04-30 15:20 ` Juan Quintela
2013-04-30 15:55   ` Chegu Vinod
2013-04-30 16:01     ` Juan Quintela
2013-04-30 17:48       ` Chegu Vinod

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=517E8979.6090103@redhat.com \
    --to=eblake@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=chegu_vinod@hp.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).