From: Roman Mamedov <rm@romanrm.net>
To: CoolCold <coolthecold@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID10 performance with 20 drives
Date: Wed, 31 May 2017 19:14:41 +0500 [thread overview]
Message-ID: <20170531191441.40240b7f@natsu> (raw)
In-Reply-To: <CAGqmV7p4_r+ca+Wq_UXcY4RDa7WwE2nWkgXF+Sn3ChwLEmkurQ@mail.gmail.com>
On Wed, 31 May 2017 19:20:10 +0700
CoolCold <coolthecold@gmail.com> wrote:
> Creation (disable write intent bitmap, with bitmap all is much worse):
> mdadm --create -c 64 -b none -n 20 -l 10 /dev/md1 /dev/sde /dev/sdf
> /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm
> /dev/sdn /dev/sdo /dev/sdp /dev/sdq /dev/sdr /dev/sds /dev/sdt
> /dev/sdu /dev/sdv /dev/sdw /dev/sdx
>
> kernel:
> [root@spare-a17484327407661 rovchinnikov]# cat /proc/version
> Linux version 3.10.0-327.el7.x86_64 (builder@kbuilder.dev.centos.org)
> (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Nov
> 19 22:10:57 UTC 2015
>
> So, the question is - why cpu usage is so high and I suppose is a limit here?
Definitely try a newer kernel, 4.4 at the very least; if no changes then 4.11.
Also I would suggest to try out larger chunk sizes, such as 512 and 1024 KB.
If you plan to use this long-term in production, also read up on the various
RAID10 data layouts and their benefits and downsides (man md, search for
"layout"; and search the Internet for benchmarks of all three).
--
With respect,
Roman
next prev parent reply other threads:[~2017-05-31 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 12:20 RAID10 performance with 20 drives CoolCold
2017-05-31 12:36 ` Joe Landman
2017-05-31 13:14 ` Adam Goryachev
2017-05-31 13:32 ` David Brown
2017-05-31 13:57 ` CoolCold
2017-05-31 14:07 ` Joe Landman
2017-05-31 14:18 ` Roman Mamedov
2017-05-31 14:35 ` Joe Landman
2017-05-31 14:14 ` Roman Mamedov [this message]
2017-06-01 5:59 ` CoolCold
2017-06-01 6:33 ` Pasi Kärkkäinen
2017-06-01 11:20 ` Roger Heflin
[not found] ` <CAMNNMLEuutwLE8xft+ZEo=ShxRP=rJEq1kzNtVbgE5RBTOYcrQ@mail.gmail.com>
2017-06-05 9:52 ` CoolCold
2017-06-05 11:34 ` Pasi Kärkkäinen
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=20170531191441.40240b7f@natsu \
--to=rm@romanrm.net \
--cc=coolthecold@gmail.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