From: OHMURA Kei <ohmura.kei@lab.ntt.co.jp>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: ohmura.kei@lab.ntt.co.jp, qemu-devel@nongnu.org,
kvm@vger.kernel.org, avi@redhat.com
Subject: [Qemu-devel] Re: [PATCH] qemu-kvm: Speed up of the dirty-bitmap-traveling
Date: Mon, 08 Feb 2010 15:14:38 +0900 [thread overview]
Message-ID: <4B6FABCE.207@lab.ntt.co.jp> (raw)
In-Reply-To: <4B6C0958.50704@siemens.com>
> Sounds logical - do you have numbers on the improvement?
Sure. The patch showed approximately 3-7 times speed up when measured with
rdtsc. The test environment and detailed results are described below.
---
tmp = rdtsc();
/* function of original code*/
t1 += rdtsc() - tmp;
tmp = rdtsc();
/* function of this patch */
t2 += rdtsc() - tmp;
---
Test Envirionment:
CPU: 4x Intel Xeon Quad Core 2.66GHz
Mem size: 6GB
kvm version: 2.6.31-17-server
qemu version: commit ed880109f74f0a4dd5b7ec09e6a2d9ba4903d9a5
Host OS: Ubuntu 9.10 (kernel 2.6.31)
Guest OS: Debian/GNU Linux lenny (kernel 2.6.26)
Guest Mem size: 512MB
We executed live migration three times. This data shows, how many times the
function is called (#called), runtime of original (orig.), runtime of this
patch (patch), speedup ratio (ratio), when live migration run.
Experimental results:
Test1: Guest OS read 3GB file, which is bigger than memory.
#called orig.(msec) patch(msec) ratio
114 1.00 0.15 6.76
132 1.57 0.25 6.26
96 1.00 0.16 6.27
Test2: Guest OS read/write 3GB file, which is bigger than memory.
#called orig.(msec) patch(msec) ratio
2196 38.1 10.6 3.59
2256 39.6 10.8 3.68
2112 36.3 10.3 3.53
> Would be great if you could provide a version for upstream as well
> because it will likely replace this qemu-kvm code on day.
O.K. We'll prepare it.
We'll also post a patch set to quicken dirty pages checking in ram_save_block
and ram_save_live soon.
next prev parent reply other threads:[~2010-02-08 6:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 10:18 [Qemu-devel] [PATCH] qemu-kvm: Speed up of the dirty-bitmap-traveling OHMURA Kei
2010-02-05 12:04 ` [Qemu-devel] " Jan Kiszka
2010-02-08 6:14 ` OHMURA Kei [this message]
2010-02-08 11:23 ` OHMURA Kei
2010-02-08 11:44 ` Jan Kiszka
2010-02-09 9:55 ` OHMURA Kei
2010-02-08 12:40 ` Avi Kivity
2010-02-09 9:54 ` OHMURA Kei
2010-02-09 10:26 ` Avi Kivity
2010-02-10 9:55 ` OHMURA Kei
2010-02-10 10:24 ` 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=4B6FABCE.207@lab.ntt.co.jp \
--to=ohmura.kei@lab.ntt.co.jp \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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).