From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: lilofile <lilofile@aliyun.com>, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: 答复:md raid5 performace 6x SSD RAID5
Date: Thu, 28 Nov 2013 00:24:45 -0600 [thread overview]
Message-ID: <5296E1AD.1040005@hardwarefreak.com> (raw)
In-Reply-To: <20131128104625.54a5fc94@natsu>
On 11/27/2013 10:46 PM, Roman Mamedov wrote:
> On Wed, 27 Nov 2013 22:41:49 -0600
> Stan Hoeppner <stan@hardwarefreak.com> wrote:
>
>>> when the stripe_cache_size is set 4096.
> ...
>> 2. A 4KB stripe cache is too small for 6 SSDs, try 8KB
>
> The stripe cache size setting is specified not in KB, but in pages per disk,
> so a value of 4096 on x86 systems means 4096*4096*6 = 96 MB of cache for the
> whole array.
Thanks Roman for correcting me on that which I know well. Typing a
trailing "KB" so often hard wires the brain and fingers I guess. My KBs
were intended to be Ks.
http://www.spinics.net/lists/raid/msg42370.html
On 04/03/13 23:20, Stan Hoeppner wrote:
...
> Formula: stripe_cache_size * 4096 bytes * drive_count = RAM usage.
To expound on the importance of this, with a handful of SSDs and a value
of 8K, throughput tends to plateau, and then slowly decreases as
stripe_cache_size is increased. The upper bound of stripe_cache_size
gains has not yet been established because the write thread peaks a core
with only a few SSDs. Multiple write threads and a larger quantity of
SSDs, or much faster SSDs, are needed to explore whether values of
16K-32K provide a meaningful increase in throughput, and whether this is
worth the RAM consumed. For instance, with 12 SSDs and
stripe_cache_size of 32768:
(((32768*4096)*12)/1048576)/1000 = 1.5 GB of RAM is consumed
When Shaohua Li completes his threading patch series it may be possible
to explore this more thoroughly.
--
Stan
next prev parent reply other threads:[~2013-11-28 6:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 11:13 ARC-1120 and MD very sloooow Jimmy Thrasibule
2013-11-22 11:17 ` Mikael Abrahamsson
2013-11-22 20:17 ` Stan Hoeppner
2013-11-22 20:17 ` Stan Hoeppner
2013-11-25 8:56 ` Jimmy Thrasibule
2013-11-26 0:45 ` Stan Hoeppner
2013-11-26 0:45 ` Stan Hoeppner
2013-11-26 2:52 ` Dave Chinner
2013-11-26 2:52 ` Dave Chinner
2013-11-26 3:58 ` Stan Hoeppner
2013-11-26 3:58 ` Stan Hoeppner
2013-11-26 6:14 ` Dave Chinner
2013-11-26 8:03 ` Stan Hoeppner
2013-11-26 8:03 ` Stan Hoeppner
2013-11-28 15:59 ` Jimmy Thrasibule
2013-11-28 15:59 ` Jimmy Thrasibule
2013-11-28 19:59 ` Stan Hoeppner
2013-11-27 13:48 ` md raid5 performace 6x SSD RAID5 lilofile
2013-11-27 13:51 ` 答复:md " lilofile
2013-11-28 4:41 ` Stan Hoeppner
2013-11-28 4:46 ` Roman Mamedov
2013-11-28 6:24 ` Stan Hoeppner [this message]
2013-11-28 10:02 ` 答复:答复:md " lilofile
2013-11-29 2:38 ` Stan Hoeppner
2013-11-29 6:23 ` Stan Hoeppner
2013-11-30 14:12 ` 答复:答复:答复:md raid5 random " lilofile
2013-12-01 14:14 ` Stan Hoeppner
2013-12-01 16:33 ` md " lilofile
2013-12-02 2:37 ` Stan Hoeppner
2013-11-28 11:54 ` 答复:答复:md raid5 " lilofile
2013-12-02 3:48 ` md " lilofile
2013-12-02 5:51 ` Stan Hoeppner
2014-09-23 3:34 ` raid sync speed lilofile
2014-09-23 5:11 ` behind_writes lilofile
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=5296E1AD.1040005@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=lilofile@aliyun.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
/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.