From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Pierre Riteau <Pierre.Riteau@irisa.fr>
Cc: qemu-devel@nongnu.org, lirans@il.ibm.com
Subject: Re: [Qemu-devel] [PATCH 0/3] Live migration without shared storage
Date: Tue, 8 Sep 2009 09:26:31 -0400 [thread overview]
Message-ID: <20090908132631.GJ23700@csclub.uwaterloo.ca> (raw)
In-Reply-To: <DCA0E3D5-9C87-4129-89D5-2F339CF6289D@irisa.fr>
On Mon, Sep 07, 2009 at 06:40:51PM +0200, Pierre Riteau wrote:
> I'm trying blk migration (not incremental) between two machines
> connected over Gigabit ethernet.
> The transfer is quite slow (about 2 MB/s over the wire).
> While the load on the sending end is low (vmstat says ~2000 blocks in/
> sec, and top says ~1% in io wait), on the receiving end I see almost 40%
> CPU in io wait, kjournald takes 20% of the CPU and vmstat reports ~14000
> blocks out/sec.
>
> Hosts are running Debian Lenny (2.6.26 32 bits), kvm-87 + your patches.
> The guest is also running Debian Lenny and is idle io wise. I tried with
> both idle and full cpu utilization, it doesn't change anything.
If you happen to be using ext3, then that might explain it. ext3 has
long had issues with performance while slowly writing a large file
(this affects mythtv a lot for example). 2.6.30 should improve things a
lot, although ext3 will never be great. ext4 is better, and hopefully
btrfs will be great (when done). xfs is also supposed to handle such
tasks very well.
--
Len Sorensen
next prev parent reply other threads:[~2009-09-08 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 9:24 [Qemu-devel] [PATCH 0/3] Live migration without shared storage lirans
2009-09-07 16:40 ` Pierre Riteau
2009-09-08 13:26 ` Lennart Sorensen [this message]
2009-09-08 13:56 ` Liran Schour
2009-09-08 14:05 ` Pierre Riteau
2009-09-08 13:44 ` Liran Schour
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=20090908132631.GJ23700@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=Pierre.Riteau@irisa.fr \
--cc=lirans@il.ibm.com \
--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).