From: Gordan Bobic <gordan@bobich.net>
To: kvm@vger.kernel.org
Subject: Re: Shouldn't cache=none be the default for drives?
Date: Wed, 07 Apr 2010 16:17:44 +0100 [thread overview]
Message-ID: <4BBCA218.1020306@bobich.net> (raw)
In-Reply-To: <4BBC992D.3050905@gmail.com>
Troels Arvin wrote:
> Hello,
>
> I'm conducting some performancetests with KVM-virtualized CentOSes. One
> thing I noticed is that guest I/O performance seems to be significantly
> better for virtio-based block devices ("drive"s) if the cache=none
> argument is used. (This was with a rather powerful storage system
> backend which is hard to saturate.)
>
> So: Why isn't cache=none be the default for drives?
Is that the right question? Or is the right question "Why is cache=none
faster?"
What did you use for measuring the performance? I have found in the past
that virtio block device was slower than IDE block device emulation.
Gordan
next prev parent reply other threads:[~2010-04-07 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 14:39 Shouldn't cache=none be the default for drives? Troels Arvin
2010-04-07 15:17 ` Gordan Bobic [this message]
2010-04-08 5:07 ` Thomas Mueller
2010-04-08 6:05 ` Michael Tokarev
2010-04-08 6:09 ` Thomas Mueller
2010-04-08 6:23 ` Thomas Mueller
2010-04-08 10:08 ` Christoph Hellwig
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=4BBCA218.1020306@bobich.net \
--to=gordan@bobich.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox