From: Nivedita Singhvi <niv@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>,
xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: Re: 2.4.29-xenU VBD performance (problem)
Date: Thu, 17 Feb 2005 09:22:57 -0800 [thread overview]
Message-ID: <4214D2F1.3040406@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1238F2@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>>But, under domU (2.4.29-xenU), using that same lvm-volume as
>>VBD, I only get around
>>10 - 12 MB/sec write performance measured in the same way.
>
>
> That's very odd -- I see virtually no loss of throughput in a domU.
>
> However, 100MB isn't really enough to get a decent measure as its likely to all still be in memory -- sync doesn't do what you think. I usually do measurements using a transfer size of 10x the memory of the system.
>
> A couple of other things to try if you still experience poor peformance:
> * use a 2.6 domU
> * use a raw partition rather than LVM
>
> We do most of our testing using 2.6 for everything, so its possible there a weird 2.4 domU to 2.6 dom0 performance bug.
Right. And to some extent, comparing 2.4 to 2.6 is
a bit of an apples to oranges comparison. There are
other differences in the kernel path - not just the
virtual block driver coming out of domU.
thanks,
Nivedita
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-17 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 4:08 2.4.29-xenU VBD performance (problem) Ian Pratt
2005-02-17 17:22 ` Nivedita Singhvi [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-18 13:03 Ian Pratt
2005-02-16 23:14 Ian Pratt
2005-02-17 16:40 ` Pasi Kärkkäinen
2005-02-14 12:24 Pasi Kärkkäinen
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=4214D2F1.3040406@us.ibm.com \
--to=niv@us.ibm.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=pasik@iki.fi \
--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.