From: Wyllys Ingersoll <wyllys.ingersoll@keepertech.com>
To: stgt@vger.kernel.org
Subject: poor rbd performance
Date: Fri, 22 Aug 2014 08:55:15 -0400 [thread overview]
Message-ID: <CAGbvivLncZVGVROR1rEP_=_kRGK7pTBdD9siOXdYJkg-H+bPFw@mail.gmail.com> (raw)
Im seeing some disappointing performance numbers using the bs_rbd backend
with a Ceph RBD pool backend over a 10GB Ethernet link.
Read operations appear to max out at about 100MB/second, regardless of
block size or amount of data being read and write operations fare much
worse, maxing out somewhere in the 40MB/second range. Any ideas why this
would be so limited?
I've tested using 'fio' as well as some other perf testing utilities. On
the same link, talking to the same ceph pool/image, using librados directly
(either through the C or Python bindings), the read performance is 5-8x
faster and write performance is 2-3x faster.
Any suggestions as to how to tune the iSCSI or bs_rbd interface to perform
better?
thanks,
Wyllys Ingersoll
next reply other threads:[~2014-08-22 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 12:55 Wyllys Ingersoll [this message]
2014-08-22 22:17 ` poor rbd performance Dan Mick
2014-08-23 13:46 ` Wyllys Ingersoll
2014-08-24 23:25 ` FUJITA Tomonori
2014-08-25 3:38 ` Wyllys Ingersoll
2014-08-26 18:23 ` Wyllys Ingersoll
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='CAGbvivLncZVGVROR1rEP_=_kRGK7pTBdD9siOXdYJkg-H+bPFw@mail.gmail.com' \
--to=wyllys.ingersoll@keepertech.com \
--cc=stgt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).