From: Reeted <reeted@shiftmail.org>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Martin Mailand <martin@tuxadero.com>,
Dongsu Park <dongsu.park@profitbricks.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio-blk performance regression and qemu-kvm
Date: Tue, 06 Mar 2012 23:07:40 +0100 [thread overview]
Message-ID: <4F568AAC.6060206@shiftmail.org> (raw)
In-Reply-To: <CAJSP0QVqHOVaa8uosbQznkwbmFJ5RC6GjCQT0cOw54DxNRTomA@mail.gmail.com>
On 03/06/12 13:59, Stefan Hajnoczi wrote:
> On Mon, Mar 5, 2012 at 4:44 PM, Martin Mailand<martin@tuxadero.com> wrote:
>> Am 05.03.2012 17:35, schrieb Stefan Hajnoczi:
>>
>>>> 1. Test on i7 Laptop with Cpu governor "ondemand".
>>>>> v0.14.1
>>>>> bw=63492KB/s iops=15873
>>>>> bw=63221KB/s iops=15805
>>>>>
>>>>> v1.0
>>>>> bw=36696KB/s iops=9173
>>>>> bw=37404KB/s iops=9350
>>>>>
>>>>> master
>>>>> bw=36396KB/s iops=9099
>>>>> bw=34182KB/s iops=8545
>>>>>
>>>>> Change the Cpu governor to "performance"
>>>>> master
>>>>> bw=81756KB/s iops=20393
>>>>> bw=81453KB/s iops=20257
>>> Interesting finding. Did you show the 0.14.1 results with
>>> "performance" governor?
>>
>>
>> Hi Stefan,
>> all results are with "ondemand" except the one where I changed it to
>> "performance"
>>
>> Do you want a v0.14.1 test with the governor on "performance"?
> 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.
Me too, I would be interested in seeing 0.14.1 being tested with
performance governor so to compare it to master with performance
governor, to make sure that this is not a regression.
BTW, I'll take the opportunity to say that 15.8 or 20.3 k IOPS are very
low figures compared to what I'd instinctively expect from a
paravirtualized block driver.
There are now PCIe SSD cards that do 240 k IOPS (e.g. "OCZ RevoDrive 3
x2 max iops") which is 12-15 times higher, for something that has to go
through a real driver and a real PCI-express bus, and can't use
zero-copy techniques.
The IOPS we can give to a VM is currently less than half that of a
single SSD SATA drive (60 k IOPS or so, these days).
That's why I consider this topic of virtio-blk performances very
important. I hope there can be improvements in this sector...
Thanks for your time
R.
WARNING: multiple messages have this Message-ID (diff)
From: Reeted <reeted@shiftmail.org>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Martin Mailand <martin@tuxadero.com>,
Dongsu Park <dongsu.park@profitbricks.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] virtio-blk performance regression and qemu-kvm
Date: Tue, 06 Mar 2012 23:07:40 +0100 [thread overview]
Message-ID: <4F568AAC.6060206@shiftmail.org> (raw)
In-Reply-To: <CAJSP0QVqHOVaa8uosbQznkwbmFJ5RC6GjCQT0cOw54DxNRTomA@mail.gmail.com>
On 03/06/12 13:59, Stefan Hajnoczi wrote:
> On Mon, Mar 5, 2012 at 4:44 PM, Martin Mailand<martin@tuxadero.com> wrote:
>> Am 05.03.2012 17:35, schrieb Stefan Hajnoczi:
>>
>>>> 1. Test on i7 Laptop with Cpu governor "ondemand".
>>>>> v0.14.1
>>>>> bw=63492KB/s iops=15873
>>>>> bw=63221KB/s iops=15805
>>>>>
>>>>> v1.0
>>>>> bw=36696KB/s iops=9173
>>>>> bw=37404KB/s iops=9350
>>>>>
>>>>> master
>>>>> bw=36396KB/s iops=9099
>>>>> bw=34182KB/s iops=8545
>>>>>
>>>>> Change the Cpu governor to "performance"
>>>>> master
>>>>> bw=81756KB/s iops=20393
>>>>> bw=81453KB/s iops=20257
>>> Interesting finding. Did you show the 0.14.1 results with
>>> "performance" governor?
>>
>>
>> Hi Stefan,
>> all results are with "ondemand" except the one where I changed it to
>> "performance"
>>
>> Do you want a v0.14.1 test with the governor on "performance"?
> 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.
Me too, I would be interested in seeing 0.14.1 being tested with
performance governor so to compare it to master with performance
governor, to make sure that this is not a regression.
BTW, I'll take the opportunity to say that 15.8 or 20.3 k IOPS are very
low figures compared to what I'd instinctively expect from a
paravirtualized block driver.
There are now PCIe SSD cards that do 240 k IOPS (e.g. "OCZ RevoDrive 3
x2 max iops") which is 12-15 times higher, for something that has to go
through a real driver and a real PCI-express bus, and can't use
zero-copy techniques.
The IOPS we can give to a VM is currently less than half that of a
single SSD SATA drive (60 k IOPS or so, these days).
That's why I consider this topic of virtio-blk performances very
important. I hope there can be improvements in this sector...
Thanks for your time
R.
next prev parent reply other threads:[~2012-03-06 22:07 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 14:36 virtio-blk performance regression and qemu-kvm Dongsu Park
2012-02-10 14:36 ` [Qemu-devel] " Dongsu Park
2012-02-12 23:55 ` Rusty Russell
2012-02-12 23:55 ` [Qemu-devel] " Rusty Russell
2012-02-21 16:45 ` Dongsu Park
2012-02-21 16:45 ` [Qemu-devel] " Dongsu Park
2012-02-21 22:16 ` Rusty Russell
2012-02-21 22:16 ` [Qemu-devel] " Rusty Russell
2012-02-13 11:57 ` Stefan Hajnoczi
2012-02-13 11:57 ` [Qemu-devel] " Stefan Hajnoczi
2012-02-21 15:57 ` Dongsu Park
2012-02-21 15:57 ` [Qemu-devel] " Dongsu Park
2012-02-21 17:27 ` Stefan Hajnoczi
2012-02-21 17:27 ` [Qemu-devel] " Stefan Hajnoczi
2012-02-22 16:48 ` Dongsu Park
2012-02-22 16:48 ` [Qemu-devel] " Dongsu Park
2012-02-22 19:53 ` Stefan Hajnoczi
2012-02-22 19:53 ` [Qemu-devel] " Stefan Hajnoczi
2012-02-28 16:39 ` Martin Mailand
2012-02-28 16:39 ` [Qemu-devel] " Martin Mailand
2012-02-28 17:05 ` Stefan Hajnoczi
2012-02-28 17:05 ` [Qemu-devel] " Stefan Hajnoczi
2012-02-28 17:15 ` Martin Mailand
2012-02-28 17:15 ` [Qemu-devel] " Martin Mailand
2012-02-29 8:38 ` Stefan Hajnoczi
2012-02-29 8:38 ` [Qemu-devel] " Stefan Hajnoczi
2012-02-29 13:12 ` Martin Mailand
2012-02-29 13:12 ` [Qemu-devel] " Martin Mailand
2012-02-29 13:44 ` Stefan Hajnoczi
2012-02-29 13:44 ` [Qemu-devel] " Stefan Hajnoczi
2012-02-29 13:52 ` Stefan Hajnoczi
2012-02-29 13:52 ` [Qemu-devel] " Stefan Hajnoczi
2012-03-05 16:13 ` Martin Mailand
2012-03-05 16:13 ` [Qemu-devel] " Martin Mailand
2012-03-05 16:35 ` Stefan Hajnoczi
2012-03-05 16:35 ` [Qemu-devel] " Stefan Hajnoczi
2012-03-05 16:44 ` Martin Mailand
2012-03-05 16:44 ` [Qemu-devel] " Martin Mailand
2012-03-06 12:59 ` Stefan Hajnoczi
2012-03-06 12:59 ` [Qemu-devel] " Stefan Hajnoczi
2012-03-06 22:07 ` Reeted [this message]
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 14:33 ` Stefan Hajnoczi
2012-03-07 10:39 ` Martin Mailand
2012-03-07 10:39 ` [Qemu-devel] " Martin Mailand
2012-03-07 11:21 ` Paolo Bonzini
2012-03-07 11:21 ` [Qemu-devel] " Paolo Bonzini
2012-03-06 14:32 ` Dongsu Park
2012-03-06 14:32 ` [Qemu-devel] " Dongsu Park
-- strict thread matches above, loose matches on Subject: below --
2012-03-08 23:56 Ross Becker
2012-03-09 10:01 ` 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=4F568AAC.6060206@shiftmail.org \
--to=reeted@shiftmail.org \
--cc=dongsu.park@profitbricks.com \
--cc=kvm@vger.kernel.org \
--cc=martin@tuxadero.com \
--cc=qemu-devel@nongnu.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 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.