From: Wido den Hollander <wido@widodh.nl>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ideal hardware spec?
Date: Fri, 24 Aug 2012 20:12:11 +0200 [thread overview]
Message-ID: <5037C3FB.200@widodh.nl> (raw)
In-Reply-To: <50379830.4000000@inktank.com>
On 08/24/2012 05:05 PM, Mark Nelson wrote:
>>>
>>> I'm running Atom D525 (SuperMicro X7SPA-HF) nodes with 4GB of RAM and
>>> 4 2TB
>> disks and a 80GB SSD (old X25-M) for journaling.
>>>
>>> That works, but what I notice is that under heavy recover the Atoms
>>> can't
>> cope with it.
>>>
>>> I'm thinking about building a couple of nodes with the AMD Brazos
>> mainboard, somelike like an Asus E35M1-I.
>>>
>>> That is not a serverboard, but it would just be a reference to see
>>> what it
>> does.
>>>
>>> One of the problems with the Atoms is the 4GB memory limitation, with
>>> the
>> AMD Brazos you can use 8GB.
>>>
>>> I'm trying to figure out a way to have a really large amount of small
>>> nodes
>> for a low price to have
>>> a massive cluster where the impact of loosing one node is very small.
>>
>> 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.
Having about ~200 of these nodes all doing not that much work.
If one fails I'd loose 0.5% of my cluster and recovery shouldn't be that
hard. Assuming here that the node crashes due to hardware failure, not
being plagued by some Ceph or BTRFS bug cluster-wide :)
Wido
next prev parent reply other threads:[~2012-08-24 18:12 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 [this message]
2012-08-24 18:23 ` Mark Nelson
2012-08-27 18:05 ` Stephen Perkins
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=5037C3FB.200@widodh.nl \
--to=wido@widodh.nl \
--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.