From: Dennis Jacobfeuerborn <dennisml@conversis.de>
To: ceph-devel@vger.kernel.org
Subject: What would a good OSD node hardware configuration look like?
Date: Mon, 05 Nov 2012 18:13:33 +0100 [thread overview]
Message-ID: <5097F3BD.2000904@conversis.de> (raw)
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?
Also what is the best setup for the journal? If I understand it correctly
then each OSD needs its own journal and that should be a separate disk but
that would be quite wasteful it seems. Would it make sense to put in two
small SSD disks in a raid-1 configuration and create a filesystem for each
OSD journal on it?
How does the number of OSDs/Nodes affect the performance of say a single dd
operation? Will blocks be distributed over the cluster and written/read in
parallel or does the number only improve concurrency rather than benefit
single threaded workloads?
Regards,
Dennis
next reply other threads:[~2012-11-05 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 17:13 Dennis Jacobfeuerborn [this message]
2012-11-06 0:14 ` What would a good OSD node hardware configuration look like? 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
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=5097F3BD.2000904@conversis.de \
--to=dennisml@conversis.de \
--cc=ceph-devel@vger.kernel.org \
/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.