From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: ming.lei@canonical.com, pl@kamp.de, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/5] linux-aio: queue requests that cannot be submitted
Date: Wed, 17 Dec 2014 16:03:05 +0100 [thread overview]
Message-ID: <54919B29.4080009@redhat.com> (raw)
In-Reply-To: <54917852.2060201@redhat.com>
On 17/12/2014 13:34, Paolo Bonzini wrote:
>
>
> On 16/12/2014 21:26, Paolo Bonzini wrote:
>>
>>> I could reproduce this very well on a random OS image that I had around.
>>> This is raw over XFS over dm-crypt, and the image is about 75% sparse
>>> (8.2G used over 35G). I only get 1-2%, but still it's visible.
>>>
>>> However I can hardly reproduce it when using a partition directly:
>>>
>>> old new
>>> mean 9.9565 9.9636 (+0.07%)
>>> stddev 0.0405 0.0537
>>> min 9.871 9.867
>>> median 9.973 9.971
>>> max 10.01 10.053
>>> count 20 20
>>>
>>> I haven't tried removing layers (e.g. fully-allocated XFS image without
>>> dm-crypt).
>>
>> Could not reproduce it with a fully-allocated XFS image, on the contrary
>> the patched QEMU is a bit faster:
>>
>> old new
>> mean 14.83325 14.82660
>> stddev 0.016930 0.010328
>> min 14.819 14.818
>> max 14.854 14.883
>> median 14.8225 14.8255
>> count 20 20
>
> Same for 50% sparse XFS image, patched QEMU a bit faster:
>
> old new
> Mean 8.31285 8.30625
> stddev 0.03690 0.03333
> min 8.277 8.276
> max 8.378 8.382
> median 8.292 8.2905
> count 20 20
Today I cannot reproduce it even on the original testcase:
old new
mean 9.64175 9.60935
stddev 0.15211 0.11117
min 9.445 9.454
max 10.102 9.835
median 9.64 9.6205
count 20 20
Some notes:
1) do you have Fam's io_get_events patch? I don't, and the tests
probably should be done with it.
2) "qemu-img bench" probably could also be changed to use AioContext
directly instead of going through GMainLoop. That said, there is some
low-hanging fruit for GMainLoop that I'll shortly send a patch for.
3) bench_cb does this:
b->sector += b->bufsize;
Should it shift right by >> BDRV_SECTOR_BITS? Or is it intended to do
the equivalent of a random read benchmark?
Paolo
next prev parent reply other threads:[~2014-12-17 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 13:52 [Qemu-devel] [PATCH v2 0/5] linux-aio: rewrite and simplify queuing code Paolo Bonzini
2014-12-11 13:52 ` [Qemu-devel] [PATCH v2 1/5] linux-aio: queue requests that cannot be submitted Paolo Bonzini
2014-12-16 11:07 ` Kevin Wolf
2014-12-16 11:28 ` Paolo Bonzini
2014-12-16 13:10 ` Kevin Wolf
2014-12-16 18:28 ` Paolo Bonzini
2014-12-16 20:26 ` Paolo Bonzini
2014-12-17 12:34 ` Paolo Bonzini
2014-12-17 15:03 ` Paolo Bonzini [this message]
2014-12-11 13:52 ` [Qemu-devel] [PATCH v2 2/5] linux-aio: track whether the queue is blocked Paolo Bonzini
2014-12-11 13:52 ` [Qemu-devel] [PATCH v2 3/5] linux-aio: rename LaioQueue idx field to "n" Paolo Bonzini
2014-12-11 13:52 ` [Qemu-devel] [PATCH v2 4/5] linux-aio: drop return code from laio_io_unplug and ioq_submit Paolo Bonzini
2014-12-11 13:52 ` [Qemu-devel] [PATCH v2 5/5] linux-aio: simplify removal of completed iocbs from the list Paolo Bonzini
2014-12-11 14:49 ` [Qemu-devel] [PATCH v2 0/5] linux-aio: rewrite and simplify queuing code Kevin Wolf
2014-12-12 17:07 ` Stefan Hajnoczi
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=54919B29.4080009@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=ming.lei@canonical.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.