From: Richard Weinberger <richard@nod.at>
To: Paolo Bonzini <pbonzini@redhat.com>,
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 16:51:18 +0200 [thread overview]
Message-ID: <53528D66.6010800@nod.at> (raw)
In-Reply-To: <53527F3A.4010705@redhat.com>
Am 19.04.2014 15:50, schrieb Paolo Bonzini:
> 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.
Problem solved. I was hunting a non-issue.
The guests had swap enabled. m(
Therefore each guest was busy with reading/writing pages do disk.
Now I see write rates between 90 and 100 MiB/s within my guests. :-)
Thanks,
//richard
prev parent reply other threads:[~2014-04-19 14:51 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
2014-04-19 14:51 ` Richard Weinberger [this message]
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=53528D66.6010800@nod.at \
--to=richard@nod.at \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox