From: Josh Durgin <josh.durgin@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: optmize librbd for iops
Date: Mon, 12 Nov 2012 23:51:48 -0800 [thread overview]
Message-ID: <50A1FC14.3010007@inktank.com> (raw)
In-Reply-To: <50A0FE96.9030708@profihost.ag>
On 11/12/2012 05:50 AM, Stefan Priebe - Profihost AG wrote:
> Hello list,
>
> are there any plans to optimize librbd for iops? Right now i'm able to
> get 50.000 iop/s via iscsi and 100.000 iop/s using multipathing with iscsi.
>
> With librbd i'm stuck to around 18.000iops. As this scales with more
> hosts but not with more disks in a vm. It must be limited by rbd
> implementation in kvm / librbd.
It'd be interesting to see which layers are most limiting in this
case - qemu/kvm, librados, or librbd.
How does rados bench with 4k writes and then 4k reads with many
concurrent IOs do?
Unfortunately there's no librbd read benchmark yet.
Josh
next prev parent reply other threads:[~2012-11-13 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 13:50 optmize librbd for iops Stefan Priebe - Profihost AG
2012-11-13 7:51 ` Josh Durgin [this message]
2012-11-13 7:55 ` Stefan Priebe
2012-11-13 8:20 ` Josh Durgin
2012-11-13 10:10 ` Stefan Priebe - Profihost AG
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=50A1FC14.3010007@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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.