From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: Dennis Jacobfeuerborn <dennisml@conversis.de>,
ceph-devel@vger.kernel.org
Subject: Re: What would a good OSD node hardware configuration look like?
Date: Tue, 06 Nov 2012 08:36:06 +0100 [thread overview]
Message-ID: <5098BDE6.3050801@profihost.ag> (raw)
In-Reply-To: <50985677.6090708@inktank.com>
Am 06.11.2012 01:14, schrieb Josh Durgin:
> On 11/05/2012 09:13 AM, Dennis Jacobfeuerborn wrote:
>> Hi,
>> I'm thinking about building a ceph cluster and I'm wondering what a good
>> configuration would look like for 4-8 (and maybe more) 2HU 8-disk or 3HU
>> 16-disk systems.
>> Would it make sense to make each disk an individual OSD or should I
>> perhaps
>> create several raid-0 and create OSDs from those?
>
> This mainly depends on your ratio of disks to cpu/ram. Generally we
> recommend 1GB ram and 1Ghz per OSD. If you've got enough cpu/ram,
> running 1 OSD/disk is pretty common. It makes recovering from a
> single disk failure faster.
Just i node while using SSDs i've seen osd processes using up to two 3.6
Ghz cores. So under heavy load and disks and network with enough speed 1
ghz might be even too low. Right now i'm calculating with 1 3.6Ghz Core
per OSD when using 10GBE and SSDs.
Greets,
Stefan
prev parent reply other threads:[~2012-11-06 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 17:13 What would a good OSD node hardware configuration look like? Dennis Jacobfeuerborn
2012-11-06 0:14 ` Josh Durgin
2012-11-06 2:49 ` Dennis Jacobfeuerborn
2012-11-06 19:30 ` Josh Durgin
2012-11-07 1:35 ` Dennis Jacobfeuerborn
2012-11-07 7:35 ` Wido den Hollander
2012-11-07 8:17 ` Gandalf Corvotempesta
2012-11-07 8:21 ` Wido den Hollander
2012-11-07 8:29 ` Gandalf Corvotempesta
2012-11-06 7:36 ` Stefan Priebe - Profihost AG [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=5098BDE6.3050801@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=dennisml@conversis.de \
--cc=josh.durgin@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.