All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Rados faster than KVM block device?
Date: Thu, 28 Jun 2012 23:17:09 +0200	[thread overview]
Message-ID: <4FECC9D5.9050202@profihost.ag> (raw)
In-Reply-To: <4FEC8252.90208@inktank.com>

Am 28.06.2012 18:12, schrieb Josh Durgin:
> On 06/28/2012 06:10 AM, Stefan Priebe - Profihost AG wrote:
>> Hello list,
>>
>> my cluster is now pretty stable i'm just wondering about the sequential
>> write values.
>>
>> With rados bench command and 16 threads i get totally different values
>> than with KVM and rbd block device.
>>
>> rados -p kvmpool bench 60 write -t 16:
>> pool size 2: Bandwidth (MB/sec):     1137.294
>> pool size 3: Bandwidth (MB/sec):     846.983
>>
>> Inside KVM with fio:
>>
>> fio --filename=$DISK --direct=1 --rw=write --bs=4M --size=200G
>> --numjobs=16 --runtime=60 --group_reporting --name=file1:
>
> There are a number of differences between running that in a vm on rbd
> and rados bench.
>
> Keep in mind it's running on a filesystem, so requests go through the
> guest fs and block layer before getting into librbd.
No it doesn't i'm testing directly the block device.

> If you don't use direct I/O, and you enable rbd writeback caching,
> librbd will be able to merge many of the smaller requests and
> you should see much better throughput.
I'm already using rbd writeback and it works good for random 4k writes, 
But it doesn't make sense for sequential 4M writes.

Stefan

  parent reply	other threads:[~2012-06-28 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 13:10 Rados faster than KVM block device? Stefan Priebe - Profihost AG
2012-06-28 16:12 ` Josh Durgin
2012-06-28 16:39   ` Tommi Virtanen
2012-06-28 21:17   ` Stefan Priebe [this message]
2012-07-02 18:33     ` Gregory Farnum

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=4FECC9D5.9050202@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@inktank.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.