public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: op-journaled fs, journal size and storage speeds
Date: Sun, 01 May 2011 23:35:30 -0500	[thread overview]
Message-ID: <4DBE3492.4060303@hardwarefreak.com> (raw)
In-Reply-To: <20110501092758.GG13542@dastard>

On 5/1/2011 4:27 AM, Dave Chinner wrote:

> Got a supplier for the custom hardware you'd need? Just use a PCIe
> SSD....

50GB OCZ RevoDrive PCIe x4 SSD MLC NAND
Dual SandForce 1200 controllers, internal RAID 0 design
70,000 write IOPS, 4KB aligned
350MB/s write sustained

$200 USD at Newegg:
http://www.newegg.com/Product/Product.aspx?Item=N82E16820227596

Current best value for a PCIe SSD suitable for dedicated log drive use, 
can fit ~22 maximum size (2GB) XFS logs.  Note the MLC NAND.  If all 
your filesystems will sustain constant high rate metadata writes, an SLC 
based product is more suitable, though price is 10-50x higher for PCIe 
SLC cards.  If you want/need the 10x increase in flash cell life of SLC 
NAND, go with this Intel SLC SATAII SSD for ~2x the $$ of the Revo. 
Note it's write IOPS is 'only' 33k, size is 32GB, 18GB less.

http://www.newegg.com/Product/Product.aspx?Item=N82E16820167013

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2011-05-02  4:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30 14:51 op-journaled fs, journal size and storage speeds Peter Grandi
2011-05-01  9:27 ` Dave Chinner
2011-05-01 18:13   ` Peter Grandi
2011-05-02  1:23     ` Dave Chinner
2011-05-02 10:40     ` Christoph Hellwig
2011-05-02  4:35   ` Stan Hoeppner [this message]

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=4DBE3492.4060303@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox