From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Khoa Huynh <khoa@us.ibm.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v5 0/4] virtio: Use ioeventfd for virtqueue notify
Date: Thu, 6 Jan 2011 16:41:50 +0000 [thread overview]
Message-ID: <AANLkTinxEbZnmFcM7z4=5b=FnRDFdOY3O9Tt6eMactOY@mail.gmail.com> (raw)
In-Reply-To: <20101219144953.GA20565@redhat.com>
Here are 4k sequential read results (cache=none) to check whether we
see an ioeventfd performance regression with virtio-blk.
The idea is to use a small blocksize with an I/O pattern (sequential
reads) that is cheap and executes quickly. Therefore we're doing many
iops and the cost virtqueue kick/notify is especially important.
We're not trying to stress the disk, we're trying to make the
difference in ioeventfd=on/off apparent.
I did 2 runs for both ioeventfd=off and ioeventfd=on. The results are
similar: 1% and 2% degradation in MB/s or iops. We'd have to do more
runs to see if the degradation is statistically significant, but the
percentage value is so low that I'm satisfied.
Are you happy to merge virtio-ioeventfd v6 + your fixups?
Full results below:
x86_64-softmmu/qemu-system-x86_64 -m 1024 -drive
if=none,file=rhel6.img,cache=none,id=system -device
virtio-blk-pci,drive=system -drive
if=none,file=/dev/volumes/storage,cache=none,id=storage -device
virtio-blk-pci,drive=storage -cpu kvm64,+x2apic -vnc :0
fio jobfile:
[global]
ioengine=libaio
buffered=0
rw=read
bs=4k
iodepth=1
runtime=2m
[job1]
filename=/dev/vdb
ioeventfd=off:
job1: (groupid=0, jobs=1): err= 0: pid=2692
read : io=2,353MB, bw=20,080KB/s, iops=5,019, runt=120001msec
slat (usec): min=20, max=1,424, avg=34.86, stdev= 7.62
clat (usec): min=1, max=11,547, avg=162.02, stdev=42.95
bw (KB/s) : min=16600, max=20328, per=100.03%, avg=20084.25, stdev=241.88
cpu : usr=1.14%, sys=13.40%, ctx=604918, majf=0, minf=29
IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
issued r/w: total=602391/0, short=0/0
lat (usec): 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%
lat (usec): 100=0.01%, 250=99.89%, 500=0.07%, 750=0.01%, 1000=0.02%
lat (msec): 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%
Run status group 0 (all jobs):
READ: io=2,353MB, aggrb=20,079KB/s, minb=20,561KB/s,
maxb=20,561KB/s, mint=120001msec, maxt=120001msec
Disk stats (read/write):
vdb: ios=601339/0, merge=0/0, ticks=112092/0, in_queue=111815, util=93.38%
ioeventfd=on:
job1: (groupid=0, jobs=1): err= 0: pid=2692
read : io=2,299MB, bw=19,619KB/s, iops=4,904, runt=120001msec
slat (usec): min=9, max=2,257, avg=40.43, stdev=11.65
clat (usec): min=1, max=28,000, avg=161.12, stdev=61.46
bw (KB/s) : min=15720, max=19984, per=100.02%, avg=19623.26, stdev=290.76
cpu : usr=1.49%, sys=19.34%, ctx=591398, majf=0, minf=29
IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
issued r/w: total=588578/0, short=0/0
lat (usec): 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%
lat (usec): 100=0.01%, 250=99.86%, 500=0.09%, 750=0.01%, 1000=0.02%
lat (msec): 2=0.01%, 4=0.01%, 10=0.01%, 50=0.01%
Run status group 0 (all jobs):
READ: io=2,299MB, aggrb=19,619KB/s, minb=20,089KB/s,
maxb=20,089KB/s, mint=120001msec, maxt=120001msec
Disk stats (read/write):
vdb: ios=587592/0, merge=0/0, ticks=110373/0, in_queue=110125, util=91.97%
Stefan
next prev parent reply other threads:[~2011-01-06 16:43 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 15:02 [Qemu-devel] [PATCH v5 0/4] virtio: Use ioeventfd for virtqueue notify Stefan Hajnoczi
2010-12-12 15:02 ` [Qemu-devel] [PATCH v5 1/4] virtio-pci: Rename bugs field to flags Stefan Hajnoczi
2010-12-12 15:02 ` [Qemu-devel] [PATCH v5 2/4] virtio-pci: Use ioeventfd for virtqueue notify Stefan Hajnoczi
2011-01-24 18:54 ` Kevin Wolf
2011-01-24 19:36 ` Michael S. Tsirkin
2011-01-24 19:48 ` Kevin Wolf
2011-01-24 19:47 ` Michael S. Tsirkin
2011-01-24 20:05 ` Kevin Wolf
2011-01-25 7:12 ` Stefan Hajnoczi
2011-01-25 9:49 ` Stefan Hajnoczi
2011-01-25 9:54 ` Stefan Hajnoczi
2011-01-25 11:27 ` Michael S. Tsirkin
2011-01-25 13:20 ` Stefan Hajnoczi
2011-01-25 14:07 ` Stefan Hajnoczi
2011-01-25 19:18 ` Anthony Liguori
2011-01-25 19:45 ` Stefan Hajnoczi
2011-01-25 19:51 ` Anthony Liguori
2011-01-25 19:59 ` Stefan Hajnoczi
2011-01-26 0:18 ` Anthony Liguori
2010-12-12 15:02 ` [Qemu-devel] [PATCH v5 3/4] virtio-pci: Don't use ioeventfd on old kernels Stefan Hajnoczi
2010-12-12 15:02 ` [Qemu-devel] [PATCH v5 4/4] docs: Document virtio PCI -device ioeventfd=on|off Stefan Hajnoczi
2010-12-12 15:14 ` [Qemu-devel] Re: [PATCH v5 0/4] virtio: Use ioeventfd for virtqueue notify Stefan Hajnoczi
2010-12-12 20:41 ` Michael S. Tsirkin
2010-12-12 20:42 ` Michael S. Tsirkin
2010-12-12 20:56 ` Michael S. Tsirkin
2010-12-12 21:09 ` Michael S. Tsirkin
2010-12-13 10:24 ` Stefan Hajnoczi
2010-12-13 10:38 ` Michael S. Tsirkin
2010-12-13 13:11 ` Stefan Hajnoczi
2010-12-13 13:35 ` Michael S. Tsirkin
2010-12-13 13:36 ` Michael S. Tsirkin
2010-12-13 14:06 ` Stefan Hajnoczi
2010-12-13 15:27 ` Stefan Hajnoczi
2010-12-13 16:00 ` Michael S. Tsirkin
2010-12-13 16:29 ` Stefan Hajnoczi
2010-12-13 16:30 ` Michael S. Tsirkin
2010-12-13 16:12 ` Michael S. Tsirkin
2010-12-13 16:28 ` Stefan Hajnoczi
2010-12-13 17:57 ` Stefan Hajnoczi
2010-12-13 18:52 ` Michael S. Tsirkin
2010-12-15 11:42 ` Stefan Hajnoczi
2010-12-15 11:48 ` Stefan Hajnoczi
2010-12-15 12:00 ` Michael S. Tsirkin
2010-12-15 12:14 ` Michael S. Tsirkin
2010-12-15 12:59 ` Stefan Hajnoczi
2010-12-16 16:40 ` Stefan Hajnoczi
2010-12-16 23:39 ` Michael S. Tsirkin
2010-12-19 14:49 ` Michael S. Tsirkin
2011-01-06 16:41 ` Stefan Hajnoczi [this message]
2011-01-06 17:04 ` Michael S. Tsirkin
2011-01-06 18:00 ` Michael S. Tsirkin
2011-01-07 8:56 ` 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='AANLkTinxEbZnmFcM7z4=5b=FnRDFdOY3O9Tt6eMactOY@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=khoa@us.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).