From: Paolo Bonzini <pbonzini@redhat.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [regression] dataplane: throughout -40% by commit 580b6b2aa2
Date: Thu, 26 Jun 2014 17:43:10 +0200 [thread overview]
Message-ID: <53AC3F8E.20808@redhat.com> (raw)
In-Reply-To: <CACVXFVNLdnHwogXV=iFyvHgDvSZxNt1XaafZfFJiCh11dzhExA@mail.gmail.com>
Il 26/06/2014 17:37, Ming Lei ha scritto:
> On Thu, Jun 26, 2014 at 11:29 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il 26/06/2014 17:14, Ming Lei ha scritto:
>>
>>> Hi Stefan,
>>>
>>> I found VM block I/O thoughput is decreased by more than 40%
>>> on my laptop, and looks much worsen in my server environment,
>>> and it is caused by your commit 580b6b2aa2:
>>>
>>> dataplane: use the QEMU block layer for I/O
>>>
>>> I run fio with below config to test random read:
>>>
>>> [global]
>>> direct=1
>>> size=4G
>>> bsrange=4k-4k
>>> timeout=20
>>> numjobs=4
>>> ioengine=libaio
>>> iodepth=64
>>> filename=/dev/vdc
>>> group_reporting=1
>>>
>>> [f]
>>> rw=randread
>>>
>>> Together with throughput drop, the latency is improved a little.
>>>
>>> With this commit, I/O block submitted to fs becomes much smaller
>>> than before, and more io_submit() need to be called to kernel, that
>>> means iodepth may become much less.
>>>
>>> I am not surprised with the result since I did compare VM I/O
>>> performance between qemu and lkvm before, which has no big qemu
>>> lock problem and handle I/O in a dedicated thread, but lkvm's block
>>> IO is still much worse than qemu from view of throughput, because
>>> lkvm doesn't submit block I/O at batch like the way of previous
>>> dataplane, IMO.
>>
>>
>> What is your elevator setting in both the host and the guest? Usually
>> deadline gives the best performance.
>
> The test is based on cfq, but I just run a quick test with deadline, looks
> no obvious difference.
Can you give us your QEMU command line?
Paolo
next prev parent reply other threads:[~2014-06-26 15:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 15:14 [Qemu-devel] [regression] dataplane: throughout -40% by commit 580b6b2aa2 Ming Lei
2014-06-26 15:29 ` Paolo Bonzini
2014-06-26 15:37 ` Ming Lei
2014-06-26 15:43 ` Paolo Bonzini [this message]
2014-06-26 15:47 ` Ming Lei
2014-06-26 15:57 ` Paolo Bonzini
2014-06-27 1:15 ` Ming Lei
2014-06-27 4:59 ` Paolo Bonzini
2014-06-27 6:23 ` Kevin Wolf
2014-06-27 7:35 ` Paolo Bonzini
2014-06-27 12:35 ` Ming Lei
2014-06-27 7:57 ` Ming Lei
2014-06-27 12:01 ` Stefan Hajnoczi
2014-06-27 12:21 ` Kevin Wolf
2014-06-27 14:50 ` Stefan Hajnoczi
2014-06-27 18:01 ` Ming Lei
2014-06-27 21:51 ` Paolo Bonzini
2014-06-28 9:58 ` Ming Lei
2014-06-30 8:08 ` Stefan Hajnoczi
2014-06-30 8:27 ` Ming Lei
2014-07-01 13:53 ` Ming Lei
2014-07-01 14:31 ` Stefan Hajnoczi
2014-07-01 14:49 ` Ming Lei
2014-07-01 16:49 ` Paolo Bonzini
2014-07-02 0:48 ` Ming Lei
2014-07-02 8:54 ` Stefan Hajnoczi
2014-07-02 9:13 ` Paolo Bonzini
2014-07-02 9:39 ` Kevin Wolf
2014-07-02 9:48 ` Paolo Bonzini
2014-07-02 10:01 ` Kevin Wolf
2014-07-02 10:23 ` Paolo Bonzini
2014-07-02 15:45 ` Ming Lei
2014-07-02 16:13 ` Ming Lei
2014-07-02 16:23 ` Paolo Bonzini
2014-07-02 16:27 ` Ming Lei
2014-07-02 16:38 ` Paolo Bonzini
2014-07-02 16:41 ` Ming Lei
2014-07-02 16:21 ` Paolo Bonzini
2014-07-03 4:54 ` Ming Lei
2014-07-03 10:29 ` Paolo Bonzini
2014-07-03 11:50 ` Ming Lei
2014-07-03 11:56 ` Paolo Bonzini
2014-07-03 12:09 ` Ming Lei
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=53AC3F8E.20808@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=tom.leiming@gmail.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).