From: Mark Nelson <mark.nelson@inktank.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Florian Haas <florian@hastexo.com>, ceph-devel@vger.kernel.org
Subject: Re: OSD nodes with >=8 spinners, SSD-backed journals, and their performance impact
Date: Tue, 15 Jan 2013 15:40:20 -0600 [thread overview]
Message-ID: <50F5CCC4.7050408@inktank.com> (raw)
In-Reply-To: <CAJH6TXgwhhzM+0OfLf_=rw5fMrrde_4tT8KjX0N-RecnQ_O6uw@mail.gmail.com>
On 01/15/2013 03:24 PM, Gandalf Corvotempesta wrote:
> 2013/1/15 Mark Nelson <mark.nelson@inktank.com>:
>> I think the 12 bay supermicro 2U "A" chassis with 12 spinning disks, 10GbE,
>> and two controllers is potentially a really nice balanced combination.
>
> Which chassis are your referring to ? I don't see any 2U with 12 front
> and rear spinning disk from supermicro. Only 3U with rear disks
>
http://www.supermicro.com/products/chassis/2U/826/SC826BA-R920LP.cfm
That chassis has 12 3.5" bays in front, with 2 2.5" bays in back. an
interesting setup could be 12 spinning disks, with 2 very fast SSDs used
for journals and OS. Would need to test it first, and not sure I like
putting the OS on the journal drives. A more modest setup would be just
to have the 12 spinning disks for data and journals and the rear drives
for the OS.
Mark
next prev parent reply other threads:[~2013-01-15 21:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 12:17 OSD nodes with >=8 spinners, SSD-backed journals, and their performance impact Florian Haas
2013-01-14 13:28 ` Tom Lanyon
2013-01-14 13:41 ` Florian Haas
2013-01-14 13:46 ` Mark Nelson
2013-01-14 14:09 ` Florian Haas
2013-01-14 17:34 ` Gregory Farnum
2013-01-14 20:17 ` Florian Haas
2013-01-15 9:31 ` Gandalf Corvotempesta
2013-01-15 17:46 ` Mark Nelson
2013-01-15 21:24 ` Gandalf Corvotempesta
2013-01-15 21:40 ` Mark Nelson [this message]
2013-01-15 21:58 ` Gandalf Corvotempesta
2013-01-16 7:41 ` Stefan Priebe - Profihost AG
2013-01-16 17:31 ` Gandalf Corvotempesta
2013-01-18 18:54 ` Simon Leinen
2013-01-18 23:48 ` Gandalf Corvotempesta
2013-01-19 8:18 ` Simon Leinen
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=50F5CCC4.7050408@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=florian@hastexo.com \
--cc=gandalf.corvotempesta@gmail.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.