From: Mark Nelson <mark.nelson@inktank.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: SSD journal suggestion
Date: Wed, 07 Nov 2012 09:01:30 -0600 [thread overview]
Message-ID: <509A77CA.5030206@inktank.com> (raw)
In-Reply-To: <CAJH6TXgrn2FVkYH=Tb67KnHJO-MWO0tKu8uNFUby=ZY-ibvLaw@mail.gmail.com>
On 11/07/2012 06:28 AM, Gandalf Corvotempesta wrote:
> 2012/11/7 Sage Weil <sage@inktank.com>:
>> On Wed, 7 Nov 2012, Gandalf Corvotempesta wrote:
>>> I'm evaluating some SSD drives as journal.
>>> Samsung 840 Pro seems to be the fastest in sequential reads and write.
>
> The 840 Pro seems to reach 485MB/s in sequential write:
> http://www.storagereview.com/samsung_ssd_840_pro_review
> --
> 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
>
I'm using Intel 510s in a test node and can do about 450MB/s per drive.
Right now I'm doing 3 journals per SSD, but topping out at about
1.2-1.4GB/s from the client perspective for the node with 15+ drives and
5 SSDs. It's possible newer versions of the code and tuning may
increase that.
TV pointed me at the new Intel DC S3700 which looks like a very
interesting option (the 100GB model for $240).
http://www.anandtech.com/show/6432/the-intel-ssd-dc-s3700-intels-3rd-generation-controller-analyzed
Mark
next prev parent reply other threads:[~2012-11-07 15:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 12:13 SSD journal suggestion Gandalf Corvotempesta
2012-11-07 12:17 ` Sage Weil
2012-11-07 12:28 ` Gandalf Corvotempesta
2012-11-07 15:01 ` Mark Nelson [this message]
2012-11-07 16:12 ` Atchley, Scott
2012-11-07 16:20 ` Mark Nelson
2012-11-07 16:35 ` Atchley, Scott
2012-11-07 16:41 ` Mark Nelson
2012-11-07 21:11 ` Martin Mailand
2012-11-07 21:14 ` Gandalf Corvotempesta
2012-11-07 21:35 ` Martin Mailand
2012-11-07 21:44 ` Stefan Priebe
2012-11-07 21:55 ` Martin Mailand
2012-11-07 21:59 ` Stefan Priebe
2012-11-07 22:13 ` Martin Mailand
2012-11-07 22:28 ` Gandalf Corvotempesta
2012-11-07 22:39 ` Martin Mailand
2012-11-07 22:51 ` Gandalf Corvotempesta
2012-11-07 23:12 ` Mark Nelson
2012-11-08 8:22 ` Gandalf Corvotempesta
2012-11-08 13:55 ` Atchley, Scott
2012-11-08 14:39 ` Mark Nelson
2012-11-08 15:00 ` Atchley, Scott
2012-11-08 15:02 ` Atchley, Scott
2012-11-08 16:19 ` Andrey Korolyov
2012-11-08 18:03 ` Atchley, Scott
2012-11-08 20:12 ` Joseph Glanville
2012-11-08 21:21 ` SSD journal suggestion / rsockets Dieter Kasper
2012-11-08 22:00 ` Joseph Glanville
2012-11-09 14:43 ` Atchley, Scott
2012-11-09 23:41 ` Joseph Glanville
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=509A77CA.5030206@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@gmail.com \
--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.