CEPH filesystem development
 help / color / mirror / Atom feed
From: "Stephen Perkins" <perkins@netmass.com>
To: ceph-devel@vger.kernel.org
Cc: 'Mark Nelson' <mark.nelson@inktank.com>
Subject: RE: Ideal hardware spec?
Date: Mon, 27 Aug 2012 13:05:32 -0500	[thread overview]
Message-ID: <00b301cd847e$8cb65e00$a6231a00$@netmass.com> (raw)
In-Reply-To: <5037C6A2.4050403@inktank.com>

>>> 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.

- 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).





  reply	other threads:[~2012-08-27 18:05 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 [this message]
2012-08-27 22:33                 ` Wido den Hollander
     [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='00b301cd847e$8cb65e00$a6231a00$@netmass.com' \
    --to=perkins@netmass.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox