From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: RAID6 r-m-w, op-journaled fs, SSDs
Date: Sat, 30 Apr 2011 14:54:02 -0500 [thread overview]
Message-ID: <4DBC68DA.1090708@hardwarefreak.com> (raw)
In-Reply-To: <20110430180213.6dcfc41c@galadriel2.home>
On 4/30/2011 11:02 AM, Emmanuel Florac wrote:
> Le Sat, 30 Apr 2011 16:27:48 +0100 vous écriviez:
>> How bad can this be when the journal is say internal for a
>> filesystem that is held on wide-stride RAID6 set?
>
> Not that bad because typically the journal is small enough to fit
> entirely in the controller cache.
>
>> I suspect very
>> very bad, with apocalyptic read-modify-write storms, eating IOPS.
>
> Not if you're using write-back cache.
Just having write back cache isn't magic by itself. The cache
management algorithm and configuration thereof are often as important,
if not more, than the total cache size on the RAID HBA or SAN controller.
Poor cache management, I'd guess, is one reason why you see Areca RAID
cards with 1-4GB cache DRAM whereas competing cards w/ similar
price/performance/features from LSI, Adaptec, and others sport 512MB.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-30 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 15:27 RAID6 r-m-w, op-journaled fs, SSDs Peter Grandi
2011-04-30 16:02 ` Emmanuel Florac
2011-04-30 19:54 ` Stan Hoeppner [this message]
2011-04-30 21:50 ` Michael Monnerie
2011-05-01 3:17 ` Stan Hoeppner
2011-05-01 9:14 ` Emmanuel Florac
2011-05-01 9:11 ` Emmanuel Florac
2011-04-30 22:27 ` NeilBrown
2011-05-01 15:31 ` Peter Grandi
2011-05-01 18:32 ` David Brown
2011-05-01 9:36 ` Dave Chinner
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=4DBC68DA.1090708@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