From: Mark Nelson <mark.nelson@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Sage Weil <sage@inktank.com>,
Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: flashcache
Date: Thu, 17 Jan 2013 07:34:40 -0600 [thread overview]
Message-ID: <50F7FDF0.6010809@inktank.com> (raw)
In-Reply-To: <D37FDADD-C230-48D8-AA09-38C474D1F395@profihost.ag>
On 01/16/2013 11:47 PM, Stefan Priebe - Profihost AG wrote:
> Hi Mark,
>
> Am 16.01.2013 um 22:53 schrieb Mark
>> With only 2 SSDs for 12 spinning disks, you'll need to make sure the SSDs are really fast. I use Intel 520s for testing which are great, but I wouldn't use them in production.
>
> Why not? I use them for a ssd only ceph cluster.
>
> Stefan
It's pretty tough to get an apples-to-apples comparison of endurance
when looking at the Intel 520 vs something like the DC S3700. If I were
actually building out a production deployment I'd probably stick with
the DC S3700 (especially if sticking journals, flashcache, and xfs
journals for 6 osds on 1 drive!). There's probably a reasonable
endurance per cost argument for a severely under-subscribed 520 (or
other similar drive) as well. It'd be an interesting study to look at
how long it takes a small enterpise drives to die vs a larger
under-subscribed consumer drive.
--
Mark Nelson
Performance Engineer
Inktank
next prev parent reply other threads:[~2013-01-17 13:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 21:22 flashcache Gandalf Corvotempesta
2013-01-16 21:29 ` flashcache Sage Weil
2013-01-16 21:42 ` flashcache Gandalf Corvotempesta
2013-01-16 21:46 ` flashcache Sage Weil
2013-01-16 21:55 ` flashcache Mark Nelson
2013-01-16 21:59 ` flashcache Gandalf Corvotempesta
2013-01-16 21:57 ` flashcache Gandalf Corvotempesta
2013-01-16 21:53 ` flashcache Mark Nelson
2013-01-16 22:04 ` flashcache Gandalf Corvotempesta
2013-01-17 5:47 ` flashcache Stefan Priebe - Profihost AG
2013-01-17 13:34 ` Mark Nelson [this message]
2013-01-17 9:46 ` flashcache Gandalf Corvotempesta
2013-01-17 13:32 ` flashcache Joseph Glanville
2013-01-17 13:37 ` flashcache Mark Nelson
2013-01-17 13:44 ` flashcache Gandalf Corvotempesta
2013-01-17 14:30 ` flashcache Atchley, Scott
2013-01-17 14:48 ` flashcache Gandalf Corvotempesta
2013-01-17 15:00 ` flashcache Atchley, Scott
2013-01-17 15:07 ` flashcache Andrey Korolyov
2013-01-17 15:47 ` flashcache Atchley, Scott
2013-01-17 16:39 ` flashcache Andrey Korolyov
2013-01-20 2:56 ` flashcache Joseph Glanville
2013-01-21 23:57 ` flashcache John Nielsen
2013-01-30 20:10 ` flashcache Joseph Glanville
2013-01-17 15:14 ` flashcache Gandalf Corvotempesta
2013-01-17 15:50 ` flashcache Atchley, Scott
2013-01-17 16:01 ` flashcache Gandalf Corvotempesta
2013-01-17 16:12 ` flashcache Atchley, Scott
2013-01-17 16:19 ` flashcache Gandalf Corvotempesta
2013-01-22 21:06 ` flashcache Atchley, Scott
2013-01-22 21:08 ` flashcache Atchley, Scott
2013-01-17 16:20 ` flashcache Stefan Priebe
2013-01-17 16:21 ` flashcache Gandalf Corvotempesta
2013-01-17 16:24 ` flashcache Stefan Priebe
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=50F7FDF0.6010809@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@gmail.com \
--cc=s.priebe@profihost.ag \
--cc=sage@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.