From: Avi Kivity <avi@redhat.com>
To: Umesh Deshpande <udeshpan@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
pbonzini@redhat.com, mtosatti@redhat.com, qemu-devel@nongnu.org,
kvm@vger.kernel.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v5 0/4] Separate thread for VM migration
Date: Thu, 25 Aug 2011 09:35:51 +0300 [thread overview]
Message-ID: <4E55ED47.1070006@redhat.com> (raw)
In-Reply-To: <4E55EBAF.1000409@redhat.com>
On 08/25/2011 09:29 AM, Umesh Deshpande wrote:
> Jitterd Test
> I ran jitterd in a migrating VM of size 8GB with and w/o the patch
> series.
> ./jitterd -f -m 1 -p 100 -r 40
> That is to report the jitter of greater than 400ms during the interval
> of 40 seconds.
>
> Jitter in ms. with the migration thread.
> Run Total (Peak)
> 1 No chatter
> 2 No chatter
> 3 No chatter
> 4 409 (360)
>
> Jitter in ms. without migration thread.
> Run Total (Peak)
> 1 4663 (2413)
> 2 643 (423)
> 3 1973 (1817)
> 4 3908 (3772)
>
> --------------------------------------------------------------
> Flood ping test : ping to the migrating VM from a third machine (data
> over 3 runs)
> Latency (ms) ping to a non-migrating VM : Avg 0.156, Max: 0.96
> Latency (ms) with migration thread : Avg 0.215, Max: 280
> Latency (ms) without migration thread : Avg 6.47, Max: 4562
>
Very impressive numbers.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Umesh Deshpande <udeshpan@redhat.com>
Cc: kvm@vger.kernel.org, quintela@redhat.com, mtosatti@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v5 0/4] Separate thread for VM migration
Date: Thu, 25 Aug 2011 09:35:51 +0300 [thread overview]
Message-ID: <4E55ED47.1070006@redhat.com> (raw)
In-Reply-To: <4E55EBAF.1000409@redhat.com>
On 08/25/2011 09:29 AM, Umesh Deshpande wrote:
> Jitterd Test
> I ran jitterd in a migrating VM of size 8GB with and w/o the patch
> series.
> ./jitterd -f -m 1 -p 100 -r 40
> That is to report the jitter of greater than 400ms during the interval
> of 40 seconds.
>
> Jitter in ms. with the migration thread.
> Run Total (Peak)
> 1 No chatter
> 2 No chatter
> 3 No chatter
> 4 409 (360)
>
> Jitter in ms. without migration thread.
> Run Total (Peak)
> 1 4663 (2413)
> 2 643 (423)
> 3 1973 (1817)
> 4 3908 (3772)
>
> --------------------------------------------------------------
> Flood ping test : ping to the migrating VM from a third machine (data
> over 3 runs)
> Latency (ms) ping to a non-migrating VM : Avg 0.156, Max: 0.96
> Latency (ms) with migration thread : Avg 0.215, Max: 280
> Latency (ms) without migration thread : Avg 6.47, Max: 4562
>
Very impressive numbers.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-08-25 6:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 3:12 [RFC PATCH v5 0/4] Separate thread for VM migration Umesh Deshpande
2011-08-24 3:12 ` [Qemu-devel] " Umesh Deshpande
2011-08-24 3:12 ` [RFC PATCH v5 1/4] MRU ram list Umesh Deshpande
2011-08-24 3:12 ` [Qemu-devel] " Umesh Deshpande
2011-08-24 3:12 ` [RFC PATCH v5 2/4] Migration thread mutex Umesh Deshpande
2011-08-24 3:12 ` [Qemu-devel] " Umesh Deshpande
2011-08-26 17:00 ` Marcelo Tosatti
2011-08-26 17:00 ` [Qemu-devel] " Marcelo Tosatti
2011-08-24 3:12 ` [RFC PATCH v5 3/4] Separate migration bitmap Umesh Deshpande
2011-08-24 3:12 ` [Qemu-devel] " Umesh Deshpande
2011-08-24 3:12 ` [RFC PATCH v5 4/4] Separate thread for VM migration Umesh Deshpande
2011-08-24 3:12 ` [Qemu-devel] " Umesh Deshpande
2011-08-24 17:19 ` [Qemu-devel] [RFC PATCH v5 0/4] " Anthony Liguori
2011-08-24 17:19 ` Anthony Liguori
2011-08-25 6:25 ` Umesh Deshpande
2011-08-25 6:25 ` [Qemu-devel] " Umesh Deshpande
2011-08-25 6:29 ` Umesh Deshpande
2011-08-25 6:29 ` [Qemu-devel] " Umesh Deshpande
2011-08-25 6:35 ` Avi Kivity [this message]
2011-08-25 6:35 ` Avi Kivity
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=4E55ED47.1070006@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=udeshpan@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 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.