From: Martin Mailand <martin@tuxadero.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: reeted@shiftmail.org, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] virtio-blk performance regression and qemu-kvm
Date: Wed, 07 Mar 2012 11:39:58 +0100 [thread overview]
Message-ID: <4F573AFE.40204@tuxadero.com> (raw)
In-Reply-To: <CAJSP0QVqHOVaa8uosbQznkwbmFJ5RC6GjCQT0cOw54DxNRTomA@mail.gmail.com>
Am 06.03.2012 13:59, schrieb Stefan Hajnoczi:
> Yes, the reason why that would be interesting is because it allows us
> to put the performance gain with master+"performance" into
> perspective. We could see how much of a change we get.
>
> Does the CPU governor also affect the result when you benchmark with
> real disks instead of ramdisk? I can see how the governor would
> affect ramdisk, but would expect real disk I/O to be impacted much
> less.
Hi,
here my results.
I tested with "fio -name iops -rw=read -size=1G -iodepth 1 -filename
/dev/vdb -ioengine libaio -direct 1 -bs 4k"
The qemu command was.
qemu-system-x86_64 --enable-kvm -m 512 -boot c \
-drive file=/home/martin/vmware/bisect_kvm/hda.img,cache=none,if=virtio
-drive file=/dev/ram0,cache=none,if=virtio
-drive file=/dev/sda2,cache=none,if=virtio
Host Kernel 3.3.0+rc4
Guest Kernel 3.0.0-16-generic ubuntu kernel
On the host I use a raw partition sda2 for the disk test, in qemu I
write with fio to /dev/vdc, though there is no fs involved.
The host disk can at max. 13K iops, in qemu I get at max 6,5K iops,
that's around about 50% overhead. All the test were with 4k reads, so I
think we are mostly latency bound.
-martin
log:
** v0.14.1 ondemand **
ram
bw=61038KB/s iops=15259
bw=66190KB/s iops=16547
disk
bw=18105KB/s iops=4526
bw=17625KB/s iops=4406
** v0.14.1 performance **
ram
bw=72356KB/s iops=18088
bw=72390KB/s iops=18097
disk
bw=27886KB/s iops=6971
bw=27915KB/s iops=6978
** master ondemand **
ram
bw=24833KB/s iops=6208
bw=27275KB/s iops=6818
disk
bw=14980KB/s iops=3745
bw=14881KB/s iops=3720
** master performance **
ram
bw=64318KB/s iops=16079
bw=63523KB/s iops=15880
disk
bw=27043KB/s iops=6760
bw=27211KB/s iops=6802
Host Disk Test (SanDisk SSD U100)
host disk ondemand
bw=48823KB/s iops=12205
bw=49086KB/s iops=12271
host disk performance
bw=55156KB/s iops=13789
bw=54980KB/s iops=13744
next prev parent reply other threads:[~2012-03-07 10:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 14:36 [Qemu-devel] virtio-blk performance regression and qemu-kvm Dongsu Park
2012-02-12 23:55 ` Rusty Russell
2012-02-21 16:45 ` Dongsu Park
2012-02-21 22:16 ` Rusty Russell
2012-02-13 11:57 ` Stefan Hajnoczi
2012-02-21 15:57 ` Dongsu Park
2012-02-21 17:27 ` Stefan Hajnoczi
2012-02-22 16:48 ` Dongsu Park
2012-02-22 19:53 ` Stefan Hajnoczi
2012-02-28 16:39 ` Martin Mailand
2012-02-28 17:05 ` Stefan Hajnoczi
2012-02-28 17:15 ` Martin Mailand
2012-02-29 8:38 ` Stefan Hajnoczi
2012-02-29 13:12 ` Martin Mailand
2012-02-29 13:44 ` Stefan Hajnoczi
2012-02-29 13:52 ` Stefan Hajnoczi
2012-03-05 16:13 ` Martin Mailand
2012-03-05 16:35 ` Stefan Hajnoczi
2012-03-05 16:44 ` Martin Mailand
2012-03-06 12:59 ` Stefan Hajnoczi
2012-03-06 22:07 ` Reeted
2012-03-07 8:04 ` Stefan Hajnoczi
2012-03-07 14:21 ` Reeted
2012-03-07 14:33 ` Stefan Hajnoczi
2012-03-07 10:39 ` Martin Mailand [this message]
2012-03-07 11:21 ` Paolo Bonzini
2012-03-06 14:32 ` Dongsu Park
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=4F573AFE.40204@tuxadero.com \
--to=martin@tuxadero.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=reeted@shiftmail.org \
--cc=stefanha@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).