From: Anthony Liguori <aliguori@us.ibm.com>
To: "Jan Kundrát" <jan.kundrat@fzu.cz>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: poor I/O performance on domU
Date: Thu, 13 Jan 2005 11:00:52 -0600 [thread overview]
Message-ID: <1105635651.25281.2.camel@localhost> (raw)
In-Reply-To: <41E69C98.7090804@fzu.cz>
On Thu, 2005-01-13 at 10:06, Jan Kundrát wrote:
> ttylinux's rootfs is exported from ext3 fs via loopback device, could it
> be the cause of troubles?
I think that's a reasonable answer. It should be easy to test though.
Try your same test on dom0 and use /dev/loopN where N is the loopback
device that has your rootfs on it.
The difference between testing /dev/loopN access on dom0 and the virtual
block device on domU should tell you the Xen-imposed performance
penalty.
I did a quick test on my system and there was a 50% slowdown using the
loopback device doing your test so I imagine it's that.
Regards,
> -jkt
--
Anthony Liguori
Samba, Linux/Windows Interoperability
Linux Technology Center (LTC) - IBM Austin
E-mail: aliguori@us.ibm.com
Phone: (512) 838-1208
Tie Line: 678-1208
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-13 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 16:06 poor I/O performance on domU Jan Kundrát
2005-01-13 17:00 ` Anthony Liguori [this message]
2005-01-13 17:08 ` Jan Kundrát
[not found] ` <1105637082.25283.12.camel@localhost>
2005-01-15 14:36 ` Jan Kundrát
2005-01-17 16:00 ` Anthony Liguori
2005-01-17 16:23 ` Jan Kundrát
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=1105635651.25281.2.camel@localhost \
--to=aliguori@us.ibm.com \
--cc=jan.kundrat@fzu.cz \
--cc=xen-devel@lists.sourceforge.net \
/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.