From: Avi Kivity <avi@redhat.com>
To: Andrew Theurer <habanero@linux.vnet.ibm.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: KVM performance vs. Xen
Date: Thu, 30 Apr 2009 16:52:02 +0300 [thread overview]
Message-ID: <49F9AD02.8070902@redhat.com> (raw)
In-Reply-To: <49F9AB2F.4020505@linux.vnet.ibm.com>
Andrew Theurer wrote:
>
>>
>>> disk: read: 17 MB/sec write: 40 MB/sec
>>
>> This could definitely cause the extra load, especially if it's many
>> small requests (compared to a few large ones).
> I don't have the request sizes at my fingertips, but we have to use a
> lot of disks to support this I/O, so I think it's safe to assume there
> are a lot more requests than a simple large sequential read/write.
Yes. Well the high context switch rate is the scheduler's way of
telling us to use linux-aio. If "lot's of disks" == 100, with a 3ms
seek time, that's already 60,000 cs/sec.
>> Really, I think linux-aio support can help here.
> Yes, I think that would work for real block devices, but would that
> help for files? I am using real block devices right now, but it would
> be nice to also see a benefit for files in a file-system. Or maybe I
> am mis-understanding this, and linux-aio can be used on files?
It could work with files with cache=none (though not qcow2 as now written).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-30 13:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 14:41 KVM performance vs. Xen Andrew Theurer
2009-04-29 15:20 ` Nakajima, Jun
2009-04-29 15:33 ` Andrew Theurer
2009-04-30 8:56 ` Avi Kivity
2009-04-30 12:49 ` Andrew Theurer
2009-04-30 13:02 ` Avi Kivity
2009-04-30 13:44 ` Andrew Theurer
2009-04-30 13:47 ` Anthony Liguori
2009-04-30 13:52 ` Avi Kivity [this message]
2009-04-30 13:45 ` Anthony Liguori
2009-04-30 13:53 ` Avi Kivity
2009-04-30 15:08 ` Anthony Liguori
2009-04-30 13:59 ` Avi Kivity
2009-04-30 14:04 ` Andrew Theurer
2009-04-30 15:11 ` Anthony Liguori
2009-04-30 15:19 ` Avi Kivity
2009-04-30 15:59 ` Anthony Liguori
2009-05-01 0:40 ` Andrew Theurer
2009-05-03 16:20 ` Avi Kivity
2009-04-30 15:09 ` Anthony Liguori
2009-04-30 16:41 ` Marcelo Tosatti
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=49F9AD02.8070902@redhat.com \
--to=avi@redhat.com \
--cc=habanero@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.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 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.