CEPH filesystem development
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Wido den Hollander <wido@widodh.nl>
Cc: Andrey Korolyov <andrey@xdel.ru>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Ideal hardware spec?
Date: Sun, 26 Aug 2012 08:29:40 -0500	[thread overview]
Message-ID: <503A24C4.5060807@inktank.com> (raw)
In-Reply-To: <503A056E.2020804@widodh.nl>

On 08/26/2012 06:15 AM, Wido den Hollander wrote:
> CC'ing this one back to the list.
>
> On 08/25/2012 09:58 PM, Andrey Korolyov wrote:
>>>
>>> They should be much more reliable than regular USB sticks due to
>>> their SLC
>>> memory.
>>>
>>> You could also take a look at these:
>>> http://www.transcend-info.com/industry/products_details.asp?CatNo=2&SerNo=14&ModNo=28&Func1No=1
>>>
>>>
>>>
>>
>> Did you tried yet those or simular sticks for CEPH journal? Right now
>> I am using Intel 313`s, which is very fast and have durability/price
>> ratio a far higher than any imaginable MLC, but they occupying one HDD
>> slot which is a quite impractical.
>>
>
> No, I haven't tried, but I think it won't work.
>
> These kind of SLC chips don't do random writes that great, you'll
> probably get something like 4MB/sec in random writes.
>
> Bigger SSDs have more cells to spread the writes over, those small
> sticks don't.
>
> The Intel 3XX or 5XX serie should work just fine for journaling, I'd
> however recommend you change the Host Protected Area to ~50% of the
> available capacity to prevent write-degradation over time.
>
> Wido
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html

Not just write degradation, but undersubscribing the SSDs should 
hopefully help them last a little longer under such a heavy write 
workload.  We are doing 3 10GB journals per 180GB Intel 520 on our 
supermicro test node.

Mark

  reply	other threads:[~2012-08-26 13:29 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
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 [this message]
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=503A24C4.5060807@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=andrey@xdel.ru \
    --cc=ceph-devel@vger.kernel.org \
    --cc=wido@widodh.nl \
    /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