All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: "Sébastien Han" <han.sebastien@gmail.com>
Cc: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Ceph benchmarks
Date: Tue, 28 Aug 2012 06:46:22 -0500	[thread overview]
Message-ID: <503CAF8E.5090106@inktank.com> (raw)
In-Reply-To: <CAOLwVUkxo5pzvHmmr1PBW98wBWuVJW==Tk34wUMNedKxNQf+4Q@mail.gmail.com>

On 08/28/2012 03:32 AM, Sébastien Han wrote:
> @Alexandre: I don't have all the machines anymore, I'll see what I can
> do :). Only the commodity cluster remains
>
> @Mark Nelson: 2) Which bench? The RADOS one?
> 3) Sorry the RAID controller doesn't support JBOD...
> 5) I still have the commodity cluster, I'll perform some little rados benchmarks

Ah, that's the problem we have with our H700s.  We do single drive 
raid0s to get around it, but it's not ideal.  Do you have two drives in 
a raid1 or just a single drive?

Some other things we've noticed on our Dell machines:

- Writeback cache is pretty much faster than writethrough cache on all 
of our tests, even sequential writes.
- Concurrent writers to a single raid group seem to tank performance.  I 
still don't know why this is, but it's making buffered IO and any direct 
IO with more than one writer top out at about 95MB/s regardless of the 
number of drives in the raid group.  (And more writers slower 
performance more).

Mark

>
> Cheers!
>
> On Tue, Aug 28, 2012 at 6:27 AM, Mark Kirkwood
> <mark.kirkwood@catalyst.net.nz>  wrote:
>> +1 to that. I've been seeing 4-6 MB/s for 4K writes for 1 OSD with 1 SSD for
>> journal and another for data [1]. Interestingly I did see some nice scaling
>> with 4K random reads: 2-4 MB/s per thread for up to 8 threads (looked like
>> it plateaued thereafter).
>>
>> Cheers
>>
>> Mark
>>
>> [1] FYI not on the box I posted about before - on a more modern pc with
>> 6Bbit/s SATA.
>>
>>
>> On 28/08/12 14:18, Mark Nelson wrote:
>>>
>>> 5) rados bench tests with smaller requests could be interesting on 15k
>>> drives.  I typically see about 1-2MB/s per OSD for 4k requests with 7200rpm
>>> SATA disks.
>>
>>

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-08-28 11:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 20:47 Ceph benchmarks Sébastien Han
2012-08-27 20:59 ` Andrey Korolyov
2012-08-28  1:40 ` Alexandre DERUMIER
2012-08-28  2:18 ` Mark Nelson
2012-08-28  4:27   ` Mark Kirkwood
2012-08-28  8:32     ` Sébastien Han
2012-08-28 11:46       ` Mark Nelson [this message]
2012-08-28 11:51 ` Plaetinck, Dieter
2012-08-28 13:11 ` Tommi Virtanen
2012-08-28 22:16   ` Sébastien Han
2012-09-08 18:16 ` Ceph benchmarks / ceph osd tell X bench Dieter Kasper
2012-09-10 17:07   ` Sébastien Han

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=503CAF8E.5090106@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=han.sebastien@gmail.com \
    --cc=mark.kirkwood@catalyst.net.nz \
    /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.