CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
To: "ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ceph-users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>
Subject: Why is librbd1 / librados2 from Firefly 20% slower than the one from dumpling?
Date: Fri, 13 Jun 2014 16:59:16 +0200	[thread overview]
Message-ID: <539B11C4.1010400@profihost.ag> (raw)

Hi,

while testint firefly i cam into the sitation where i had a client where 
the latest dumpling packages where installed (0.67.9).

As my pool has hashppool false and the tunables are set to default it 
can talk to my firefly ceph sotrage.

For random 4k writes using fio with librbd and 32 jobs and an iodepth of 32.

I get these results:

librbd / librados2 from dumpling:
   write: io=3020.9MB, bw=103083KB/s, iops=25770, runt= 30008msec
   WRITE: io=3020.9MB, aggrb=103082KB/s, minb=103082KB/s, 
maxb=103082KB/s, mint=30008msec, maxt=30008msec

librbd / librados2 from firefly:
   write: io=7344.3MB, bw=83537KB/s, iops=20884, runt= 90026msec
   WRITE: io=7344.3MB, aggrb=83537KB/s, minb=83537KB/s, maxb=83537KB/s, 
mint=90026msec, maxt=90026msec

Stefan

             reply	other threads:[~2014-06-13 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 14:59 Stefan Priebe [this message]
     [not found] ` <539B11C4.1010400-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2014-06-26  0:17   ` Why is librbd1 / librados2 from Firefly 20% slower than the one from dumpling? Gregory Farnum
2014-06-26  2:53     ` [ceph-users] " Christian Balzer
     [not found]     ` <CAPYLRzjL1JrgsThUejDHQsG3qcK1ZTXgcO2mHEuoHN-FbwVwsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-27  6:49       ` Stefan Priebe - Profihost AG
2014-07-01 22:51         ` [ceph-users] " Gregory Farnum
     [not found]           ` <CAPYLRzhJ_3WkWSFUAx+w+gt5PTLD7SYmSyQ-xPRZ31ahN4a1Ag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02 13:01             ` Stefan Priebe - Profihost AG
     [not found]               ` <53B40292.2000108-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2014-07-02 13:07                 ` Haomai Wang
     [not found]                   ` <CACJqLyZYpEJYUn5m5B4LCGGfszY_xPjui5q7HShQuotBkVDt4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02 13:12                     ` Stefan Priebe - Profihost AG
2014-07-02 14:00                       ` [ceph-users] " Gregory Farnum
     [not found]                         ` <CAPYLRziFqZYFn4E22oE+-HXXcRppzwY=h2TbDuCErSixzZ=eWQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02 19:00                           ` Stefan Priebe
     [not found]                             ` <53B456E3.1060909-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2014-07-02 19:36                               ` Gregory Farnum
2014-07-02 19:44                                 ` [ceph-users] " Stefan Priebe
     [not found]                                   ` <53B46106.7050306-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2014-07-02 19:46                                     ` 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=539B11C4.1010400@profihost.ag \
    --to=s.priebe-2lf/h1ldwehr5kwtpvns9a@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.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