From: Stan Hoeppner <stan@hardwarefreak.com>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Cc: linux-raid@vger.kernel.org, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: md-RAID5/6 stripe_cache_size default value vs performance vs memory footprint
Date: Sat, 21 Dec 2013 19:41:37 -0600 [thread overview]
Message-ID: <52B64351.4040806@hardwarefreak.com> (raw)
In-Reply-To: <52B57912.5080000@hardwarefreak.com>
On 12/21/2013 5:18 AM, Stan Hoeppner wrote:
...
> For example, I assisted a user with 5x Intel SSDs back in January and
> his system required 4096, or 80MB of RAM for stripe cache, to reach
> maximum write throughput of the devices. This yielded 600MB/s or 60%
> greater throughput than 2048, or 40MB RAM for cache. In his case 60MB
> more RAM than the default was well worth the increase as the machine was
> an iSCSI target server with 8GB RAM.
Correction here. I said above that 80MB was 60MB greater than the
default for his 5 drives. This should have said 75MB greater than the
default which is 1MB per member device, or 5MB for 5 drives.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-22 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52B102FF.8040404@pzystorm.de>
[not found] ` <52B2FE9E.50307@hardwarefreak.com>
[not found] ` <52B41B67.9030308@pzystorm.de>
2013-12-20 22:43 ` XFS blocked task in xlog_cil_force_lsn Arkadiusz Miśkiewicz
2013-12-21 11:18 ` md-RAID5/6 stripe_cache_size default value vs performance vs memory footprint Stan Hoeppner
2013-12-21 12:20 ` Piergiorgio Sartor
2013-12-22 1:41 ` Stan Hoeppner [this message]
2013-12-26 8:55 ` Christoph Hellwig
2013-12-26 9:24 ` Stan Hoeppner
2013-12-26 22:14 ` NeilBrown
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=52B64351.4040806@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=arekm@maven.pl \
--cc=linux-raid@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).