All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mehdi Abaakouk <sileht@sileht.net>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ceph Benchmark HowTo
Date: Thu, 2 Aug 2012 17:48:19 +0200	[thread overview]
Message-ID: <20120802154818.GA3315@mail.sileht.net> (raw)
In-Reply-To: <501937F4.4080401@inktank.com>

[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]

On Wed, Aug 01, 2012 at 09:06:44AM -0500, Mark Nelson wrote:
> I haven't actually used bonnie++ myself, but I've read some rather
> bad reports from various other people in the industry.  Not sure how
> much it's changed since then...
> 
> https://blogs.oracle.com/roch/entry/decoding_bonnie
> http://www.quora.com/What-are-some-file-system-benchmarks
> http://scalability.org/?p=1685
> http://scalability.org/?p=1688
> 
> I'd say to just take extra care to make sure that that it's behaving
> the way you intended it to (probably good advice no matter which
> benchmark you use!)

Thanks, for this good links :), I have started to try fio too for its
flexibility.

> >All results are good, my benchmark is clearly limited by my network
> >connection ~ 110MB/s.
> 
> Gigabit Ethernet is definitely going to be a limitation with large
> block sequential IO for most modern disks.  I'm concerned with your
> 6 client numbers though.  I assume those numbers are per client?
> Even so, with 10 OSDs that performance is pretty bad!  Are you
> getting a good distribution of writes across all OSDs?  Consistent
> throughput over time on each?

This is a network issue too, the 6 clients tests are not really 
representatives, all clients share the same 1 gigabit link, I will 
acquire more hardwares to be more realistic soon (and replace these
results).

Some precisions have been added to the benchmark page.

> >In exception of the rest-api bench, the value seems really low.
> > ...
> >Is my rest-bench result normal ? Have I missed something ?
> 
> You may want to try increasing the number of concurrent rest-bench
> operations.  Also I'd explicitly specify the number of PGs for the
> pool you create to make sure that you are getting a good
> distribution.

During my test the number of PGs is 640 for 10 OSDs, I have tried with more
concurrent operation 32 and 64, but the result is almost the same with
more latency. 


Cheers,
-- 
Mehdi Abaakouk for eNovance
mail: sileht@sileht.net
irc: sileht

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-08-02 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 14:43 Ceph Benchmark HowTo Mehdi Abaakouk
2012-07-24 15:55 ` Mark Nelson
2012-07-24 16:19   ` Tommi Virtanen
2012-07-25 19:39     ` Florian Haas
2012-07-25 16:37   ` Mehdi Abaakouk
2012-07-25 20:06 ` Florian Haas
2012-07-25 20:25   ` Gregory Farnum
2012-07-25 20:35     ` Tommi Virtanen
2012-07-25 21:31   ` Mehdi Abaakouk
2012-07-31 12:31 ` Mehdi Abaakouk
2012-08-01 14:06   ` Mark Nelson
2012-08-02 15:48     ` Mehdi Abaakouk [this message]

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=20120802154818.GA3315@mail.sileht.net \
    --to=sileht@sileht.net \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@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.