From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, ryanh@us.ibm.com, aliguro@us.ibm.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Why qemu write/rw speed is so low?
Date: Fri, 9 Sep 2011 11:38:01 +0100 [thread overview]
Message-ID: <20110909103801.GA26148@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <20110909094436.GB23929@f15.cn.ibm.com>
On Fri, Sep 09, 2011 at 05:44:36PM +0800, Zhi Yong Wu wrote:
> Today, i did some basical I/O testing, and suddenly found that qemu write and rw speed is so low now, my qemu binary is built on commit 344eecf6995f4a0ad1d887cec922f6806f91a3f8.
>
> Do qemu have regression?
>
> The testing data is shown as below:
>
> 1.) write
>
> test: (g=0): rw=write, bs=512-512/512-512, ioengine=libaio, iodepth=1
Please post your QEMU command-line. If your -drive is using
cache=writethrough then small writes are slow because they require the
physical disk to write and then synchronize its write cache. Typically
cache=none is a good setting to use for local disks.
The block size of 512 bytes is too small. Ext4 uses a 4 KB block size,
so I think a 512 byte write from the guest could cause a 4 KB
read-modify-write operation on the host filesystem.
You can check this by running btrace(8) on the host during the
benchmark. The blktrace output and the summary statistics will show
what I/O pattern the host is issuing.
I suggest changing your fio block size to 8 KB if you want to try a
small block size. If you want a large block size, try 64 KB or 128 KB.
Stefan
next prev parent reply other threads:[~2011-09-09 10:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 9:44 [Qemu-devel] Why qemu write/rw speed is so low? Zhi Yong Wu
2011-09-09 10:38 ` Stefan Hajnoczi [this message]
2011-09-09 13:48 ` Zhi Yong Wu
2011-09-09 13:54 ` Stefan Hajnoczi
2011-09-09 14:04 ` Kevin Wolf
2011-09-09 15:27 ` Stefan Hajnoczi
2011-09-11 13:32 ` Christoph Hellwig
2011-09-09 14:09 ` Zhi Yong Wu
2011-09-13 2:38 ` Zhi Yong Wu
2011-09-13 2:52 ` Zhi Yong Wu
2011-09-13 7:14 ` Stefan Hajnoczi
2011-09-13 9:25 ` Zhi Yong Wu
2011-09-13 10:14 ` Stefan Hajnoczi
2011-09-13 10:27 ` Zhi Yong Wu
2011-09-14 2:42 ` Zhi Yong Wu
2011-09-14 14:17 ` Stefan Hajnoczi
2011-09-15 9:04 ` Zhi Yong Wu
2011-09-13 7:15 ` Stefan Hajnoczi
2011-09-13 8:31 ` Zhi Yong Wu
2011-09-13 8:49 ` Stefan Hajnoczi
2011-09-13 8:54 ` Zhi Yong Wu
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=20110909103801.GA26148@stefanha-thinkpad.localdomain \
--to=stefanha@linux.vnet.ibm.com \
--cc=aliguro@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
--cc=wuzhy@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).