All of lore.kernel.org
 help / color / mirror / Atom feed
From: john cooper <john.cooper@third-harmonic.com>
To: Lucas Nussbaum <lucas@lucas-nussbaum.net>
Cc: kvm@vger.kernel.org, john.cooper@redhat.com
Subject: Re: bad virtio disk performance
Date: Mon, 27 Apr 2009 13:36:05 -0400	[thread overview]
Message-ID: <49F5ED05.6020703@third-harmonic.com> (raw)
In-Reply-To: <20090427151204.GA16943@xanadu.blop.info>

Lucas Nussbaum wrote:
> Hi,
> 
> I'm experiencing bad disk I/O performance using virtio disks.
> 
> I'm using Linux 2.6.29 (host & guest), kvm 84 userspace.
> On the host, and in a non-virtio guest, I get ~120 MB/s when writing
> with dd (the disks are fast RAID0 SAS disks).

Could you provide detail of the exact type and size
of i/o load you were creating with dd?

Also the full qemu cmd line invocation in both
cases would be useful.

> In a guest with a virtio disk, I get at most ~32 MB/s.

Which non-virtio interface was used for the
comparison?

> The rest of the setup is the same. For reference, I'm running kvm -drive
> file=/tmp/debian-amd64.img,if=virtio.
> 
> Is such performance expected? What should I check?

Not expected, something is awry.

blktrace(8) run on the host will shed some light
on the type of i/o requests issued by qemu in both
cases.

-john


-- 
john.cooper@third-harmonic.com

  reply	other threads:[~2009-04-27 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 15:12 bad virtio disk performance Lucas Nussbaum
2009-04-27 17:36 ` john cooper [this message]
2009-04-27 18:28   ` Lucas Nussbaum
2009-04-27 23:40     ` john cooper
2009-04-28 10:56       ` Lucas Nussbaum
2009-04-28 11:48         ` Lucas Nussbaum
2009-04-28 11:55           ` Avi Kivity
2009-04-28 14:35             ` Lucas Nussbaum

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=49F5ED05.6020703@third-harmonic.com \
    --to=john.cooper@third-harmonic.com \
    --cc=john.cooper@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lucas@lucas-nussbaum.net \
    /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.