All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Richard Weinberger <richard.weinberger@gmail.com>,
	kvm <kvm@vger.kernel.org>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: Very poor write performance
Date: Sat, 19 Apr 2014 09:50:50 -0400	[thread overview]
Message-ID: <53527F3A.4010705@redhat.com> (raw)
In-Reply-To: <CAFLxGvwPdtMxO2e_i4XdLd3tPxSVXceKk6O+z7U5jqdRXQe_nA@mail.gmail.com>

Il 19/04/2014 08:04, Richard Weinberger ha scritto:
> Hi!
>
> I hope this is the right place to ask. :)
>
> On a rather recent x86_64 server I'm facing very bad write performance.
> The Server is a 8 Core Xeon E5 with 64GiB ram.
>
> Storage is a ext4 filesystem on top of LVM which is backed by DRBD.
> On the host side dd can easily write with 100MiB/s to the ext4.
> OS is Centos6 with kernel 3.12.x.
>
> Within a KVM Linux guest the seq write throughput is always only
> between 20 and 30MiB/s.
> The guest OS is Centos6, it uses virtio-blk, cache=none, io=natvie and
> the deadline IO scheduler.
>
> The worst thing is that the total IO bandwidth of KVM seems to 30MiB/s.
> If I run the same write benchmark within 5 guests each one achieves
> only 6 or 7 MiB/s.
> I see the same values also if the guest writes directly to a disk like vdb.
> Having the guest disk directly on LVM instead of a ext4 file also didn't help.
> It really looks like 30MiB/s is the upper bound for KVM disk IO.

As a first guess, can you try XFS or direct DRBD?  There seems to be a 
bug in ext4 that limits queue depth to a very low value.

Paolo

  reply	other threads:[~2014-04-19 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 12:04 Very poor write performance Richard Weinberger
2014-04-19 13:50 ` Paolo Bonzini [this message]
2014-04-19 14:51   ` Richard Weinberger

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=53527F3A.4010705@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=stefanha@redhat.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.