From: Michael Tokarev <mjt@tls.msk.ru>
To: Thomas Mueller <thomas@chaschperli.ch>
Cc: kvm@vger.kernel.org
Subject: Re: Shouldn't cache=none be the default for drives?
Date: Thu, 08 Apr 2010 10:05:09 +0400 [thread overview]
Message-ID: <4BBD7215.3080204@msgid.tls.msk.ru> (raw)
In-Reply-To: <hpjo9m$tv8$1@dough.gmane.org>
08.04.2010 09:07, Thomas Mueller wrote:
[]
> This helped alot:
>
> I enabled "deadline" block scheduler instead of the default "cfq" on the
> host system. tested with: Host Debian with scheduler deadline, Guest
> Win2008 with Virtio and cache=none. (26MB/s to 50MB/s boost measured)
> Maybe this is also true for Linux/Linux.
>
> I expect that scheduler "noop" for linux guests would be good.
Hmm. I wonder why it helped. In theory, host scheduler should not
change anything for cache=none case, at least for raw partitions of
LVM volumes. This is because with cache=none, the virtual disk
image is opened with O_DIRECT flag, which means all I/O bypasses
host scheduler and buffer cache.
I tried a few quick tests here, -- with LVM volumes it makes no
measurable difference. But if the guest disk images are on
plain files (also raw), scheduler makes some difference, and
indeed deadline works better. Maybe you were testing with
plain files instead of block devices?
Thanks!
/mjt
next prev parent reply other threads:[~2010-04-08 6:05 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
2010-04-08 5:07 ` Thomas Mueller
2010-04-08 6:05 ` Michael Tokarev [this message]
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=4BBD7215.3080204@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kvm@vger.kernel.org \
--cc=thomas@chaschperli.ch \
/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