From: Stan Hoeppner <stan@hardwarefreak.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Mike Dacre <mike.dacre@gmail.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Sudden File System Corruption
Date: Sun, 08 Dec 2013 18:58:07 -0600 [thread overview]
Message-ID: <52A5159F.2060309@hardwarefreak.com> (raw)
In-Reply-To: <20131208160339.5c45ab91@galadriel.home>
On 12/8/2013 9:03 AM, Emmanuel Florac wrote:
> Le Sat, 07 Dec 2013 23:22:07 -0600 vous écriviez:
>
>>> Thanks for the great advice, I think you are on to something
>>> there. I will
>>
>> You're welcome. Full disclosure: I should have mentioned that I
>> haven't used CacheCade yet myself. My statements WRT performance are
>> based on available literature and understanding of the technology.
>
> I didn't test thoroughly cachecade though I have a license code
> somewhere, however I've used the equivalent Adaptec feature and one SSD
> roughly double the IOPS of a RAID-6 array of 15k RPM SAS drives from
> about 4200 IOPS to 7500 IOPS.
Emmanuel do you recall which SSD you used here? 7500 IOPS is very low
by today's standards. What I'm wondering is if you had an older low
IOPS SSD, or, a modern high IOPS rated SSD that performed way below its
specs in this application.
The Samsung 840 Pro I recommended is rated at 90K 4K write IOPS and
actually hits that mark in IOmeter testing at a queue depth of 7 and
greater:
http://www.tomshardware.com/reviews/840-pro-ssd-toggle-mode-2,3302-3.html
Its processor is a 3 core ARM Cortex R4 so it should excel in this RAID
cache application, which will likely have gobs of concurrency, and thus
a high queue depth.
Found a review of CacheCade 2.0. Their testing shows near actual SSD
throughput. The Micron P300 has 44K/16K read/write IOPS and their
testing hits 30K. So you should be able to hit close to ~90K read/write
IOPS with the Samsung 840s.
http://www.storagereview.com/lsi_megaraid_cachecade_pro_20_review
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-09 0:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 2:55 Sudden File System Corruption Mike Dacre
2013-12-05 3:40 ` Dave Chinner
2013-12-05 3:46 ` Mike Dacre
2013-12-05 3:59 ` Dave Chinner
2013-12-05 8:10 ` Stan Hoeppner
[not found] ` <CAPd9ww9hsOFK6pxqRY-YtLLAkkJHCuSi1BaM4n9=2XTjNVAn2Q@mail.gmail.com>
2013-12-05 15:58 ` Fwd: " Mike Dacre
2013-12-06 8:58 ` Stan Hoeppner
[not found] ` <CAPd9ww8+W2VX2HAfxEkVN5mL1a_+=HDAStf1126WSE33Vb=VsQ@mail.gmail.com>
2013-12-06 23:15 ` Fwd: " Mike Dacre
2013-12-07 11:12 ` Stan Hoeppner
2013-12-07 18:36 ` Mike Dacre
2013-12-08 5:22 ` Stan Hoeppner
2013-12-08 15:03 ` Emmanuel Florac
2013-12-09 0:58 ` Stan Hoeppner [this message]
2013-12-09 1:40 ` Dave Chinner
2013-12-09 19:51 ` Stan Hoeppner
2013-12-09 22:21 ` Dave Chinner
2013-12-09 22:30 ` Emmanuel Florac
2013-12-10 3:39 ` Stan Hoeppner
2013-12-10 8:45 ` Emmanuel Florac
2013-12-09 22:24 ` Emmanuel Florac
2013-12-09 9:49 ` Emmanuel Florac
2013-12-05 17:40 ` Ben Myers
[not found] ` <20131205175053.GG1935@sgi.com>
[not found] ` <CAPd9ww9YFbMEe-dM96zHsbRJgQuBHfF=ipromch1Yw6SzPUftg@mail.gmail.com>
[not found] ` <20131206002308.GS10553@sgi.com>
[not found] ` <CAPd9ww8XDzGbSZsEEoCmSuJ+KBYUWqHeRON1sFr6bG1fZ6af7w@mail.gmail.com>
[not found] ` <20131206225612.GU10553@sgi.com>
2013-12-06 23:15 ` Mike Dacre
2013-12-08 22:20 ` Dave Chinner
2013-12-09 19:04 ` Eric Sandeen
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=52A5159F.2060309@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=eflorac@intellique.com \
--cc=mike.dacre@gmail.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