From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Rados faster than KVM block device?
Date: Thu, 28 Jun 2012 15:10:22 +0200 [thread overview]
Message-ID: <4FEC57BE.9060703@profihost.ag> (raw)
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:
pool size 2:
write: io=32984MB, bw=562046KB/s, iops=137 , runt= 60094msec
pool size 3:
write: io=29124MB, bw=496024KB/s, iops=121 , runt= 60124msec
Even when i change the pool size to 3 i get with fio 520MB/s.
Any ideas? Is this expected?
Greets
Stefan
next reply other threads:[~2012-06-28 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 13:10 Stefan Priebe - Profihost AG [this message]
2012-06-28 16:12 ` Rados faster than KVM block device? Josh Durgin
2012-06-28 16:39 ` Tommi Virtanen
2012-06-28 21:17 ` Stefan Priebe
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=4FEC57BE.9060703@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@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 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.