public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Asdo <asdo@shiftmail.org>
To: kvm@vger.kernel.org
Subject: Performance of virtio-blk?
Date: Sat, 06 Mar 2010 15:58:12 +0100	[thread overview]
Message-ID: <4B926D84.3020106@shiftmail.org> (raw)

Dear kvm developers
firstly thank you for doing such a great job on KVM.

Following this list I see great ongoing progresses on virtio-net, now 
even more with the vhost
but I see virtio-blk very rarely mentioned.

We have an old kvm installation (host kernel is also old at 2.6.24) and 
I don't seem to be able to get good performances out of virtio-blk, I 
think it doesn't surpass 40MB/sec (difficult to benchmark as there are 
many VMs running now), while we have a large RAID on the host. We would 
really need fast disk access more than network access.

How is the speed on the newest KVMs and kernels? (suppose the HD is not 
the bottleneck, e.g. on a fast RAID)

Also is there any guide on how to tune it?

Is a vhost-blk planned?  For vhost-net I read you got to the 7Gbit/sec! 
700MB/sec disk access could be enough :-D

                 reply	other threads:[~2010-03-06 17:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B926D84.3020106@shiftmail.org \
    --to=asdo@shiftmail.org \
    --cc=kvm@vger.kernel.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