All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: Stephen Perkins <perkins@netmass.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ideal hardware spec?
Date: Tue, 28 Aug 2012 00:33:25 +0200	[thread overview]
Message-ID: <503BF5B5.6000100@widodh.nl> (raw)
In-Reply-To: <00b301cd847e$8cb65e00$a6231a00$@netmass.com>



On 08/27/2012 08:05 PM, Stephen Perkins wrote:
>>>> Given that "massive" is a relative term, I am as well... but I'm
>>>> also trying to reduce the footprint (power and space) of that
>>>> "massive" cluster.
>>>> I also
>>>> want to start small (1/2 rack) and scale as needed.
>>>
>>> If you do end up testing Brazos processes, please post your results!
>>> I think it really depends on what kind of performance you are aiming for.
>>> Our stock 2U test boxes have 6-core opterons, and our SC847a has dual
>>> 6-core low power Xeon E5s. At 10GbE+ these are probably going to be
>>> pushed pretty hard, especially during recovery.
>>>
>>
>> I'm aiming for a Ceph cluster of a couple of hundred TB consisting out
>> of 5 or 6 racks full of 1U machines with each 4x 1TB.
>
> Thinking along the lines of the approach of many 1U by 4 drive host (as
> above) with no hardware RAID... what are the thoughts between SATAII (3G/s)
> vs SATAIII (6G/s) and on 1G Ethernet versus 10G Ethernet.
>

While SATA3 offers more bandwidth you won't benefit that much with 
7200RPM disks.

Buffer writes might go a bit faster, but it won't be shocking.

You will however notice the difference when using a SSD for journaling, 
since the new SSDs are able to utilize the SATA3 bandwidth much better.

I think that 10G would be overkill for a node with just 4 OSDs running 
on 4 disks in total, but you might want to look at trunking 2 1Gb NIC's 
with LACP?

> - Steve
>
> P.S.  I will be assuming a replication level of 3 copies and would probably
> be looking at 10 nodes or less initially.  Maybe populating with 6 drives
> instead of 4 (if I can find the right chassis).
>

I'd go with 3 as well. Going with 2 would cause you to limp whenever 
just one machine/disk fails.

If you want to go for 6 drives in 1U you'd be looking at 2.5" drives. 
It's a bummer they are still so expensive when looking at price per GB.

Wido

  reply	other threads:[~2012-08-27 22:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 13:55 Ideal hardware spec? Jonathan Proulx
2012-08-22 14:17 ` Wido den Hollander
2012-08-22 14:39   ` Stephen Perkins
2012-08-23  8:24     ` Wido den Hollander
2012-08-24 14:17       ` Stephen Perkins
2012-08-24 14:41         ` Joe Landman
2012-08-24 15:05         ` Mark Nelson
2012-08-24 16:30           ` Sławomir Skowron
2012-08-24 18:12           ` Wido den Hollander
2012-08-24 18:23             ` Mark Nelson
2012-08-27 18:05               ` Stephen Perkins
2012-08-27 22:33                 ` Wido den Hollander [this message]
     [not found]             ` <00ae01cd823e$84e2ed20$8ea8c760$@netmass.com>
2012-08-25 11:48               ` Wido den Hollander
2012-08-24 16:12         ` Tommi Virtanen
2012-08-24 18:09         ` Wido den Hollander
2012-08-22 15:46   ` Jonathan Proulx
2012-08-23  9:59     ` Wido den Hollander
     [not found]       ` <CABYiri_-73UyTKHcHWDZdjqb=rozjraVzxd166NZV2ir53tduA@mail.gmail.com>
2012-08-26 11:15         ` Wido den Hollander
2012-08-26 13:29           ` Mark Nelson
2012-08-22 14:41 ` Mark Nelson
2012-08-28  0:02   ` Curtis C.
2012-08-28  1:18     ` Mark Nelson

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=503BF5B5.6000100@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=perkins@netmass.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.