From: Stan Hoeppner <stan@hardwarefreak.com>
To: lilofile <lilofile@aliyun.com>, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: 答复:答复:md raid5 performace 6x SSD RAID5
Date: Fri, 29 Nov 2013 00:23:46 -0600 [thread overview]
Message-ID: <529832F2.8010206@hardwarefreak.com> (raw)
In-Reply-To: <5297FE1C.6080504@hardwarefreak.com>
On 11/28/2013 8:38 PM, Stan Hoeppner wrote:
> On 11/28/2013 4:02 AM, lilofile wrote:
>> thank you for your advise. now I have test multi-thread patch, the single raid5 performance improve 30%.
>>
>> but I have another problem,when write on single raid,write performance is approx 1.1GB/s
> ...
>> [1]- Done dd if=/dev/zero of=/dev/md126 count=100000 bs=1M
>> [2]+ Done dd if=/dev/zero of=/dev/md127 count=100000 bs=1M
>
> No. This is not a parallel IO test.
>
> ...
>> To address #3 use FIO or a similar testing tool that can issue IOs in
>> parallel. With SSD based storage you will never reach maximum
>> throughput with a serial data stream.
>
> This is a parallel IO test, one command line:
>
> ~# fio --directory=/dev/md126 --zero_buffers --numjobs=16
> --group_reporting --blocksize=64k --ioengine=libaio --iodepth=16
> --direct=1 --size=64g --name=read --rw=read --stonewall --name=write
> --rw=write --stonewall
Correction. The --size value is per job, not per fio run. We use 16
jobs in parallel to maximize the hardware throughput. So use --size=4g
for 64GB total written in the test. If you use --size=64g as I stated
above you'll write 1TB total in the test, and it will take forever to
finish. With --size=4g the read test should take ~30 seconds and the
write test ~40s, not including the fio initialization time.
> Normally this targets a filesystem, not a raw block device. This
> command line should work for a raw md device.
--
Stan
next prev parent reply other threads:[~2013-11-29 6:23 UTC|newest]
Thread overview: 28+ 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-25 8:56 ` Jimmy Thrasibule
2013-11-26 0:45 ` Stan Hoeppner
2013-11-26 2:52 ` Dave Chinner
2013-11-26 3:58 ` Stan Hoeppner
2013-11-26 6:14 ` Dave Chinner
2013-11-26 8:03 ` Stan Hoeppner
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
2013-11-28 10:02 ` 答复:答复:md " lilofile
2013-11-29 2:38 ` Stan Hoeppner
2013-11-29 6:23 ` Stan Hoeppner [this message]
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=529832F2.8010206@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=lilofile@aliyun.com \
--cc=linux-raid@vger.kernel.org \
/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).