Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Joe Landman <joe.landman@gmail.com>
To: CoolCold <coolthecold@gmail.com>,
	Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID10 performance with 20 drives
Date: Wed, 31 May 2017 10:07:50 -0400	[thread overview]
Message-ID: <87cf573c-775c-ee32-1beb-d45702434366@gmail.com> (raw)
In-Reply-To: <CAGqmV7pdiTKRZY2gnPH0QO7eWLAZVWKZc8tqE1t_rzENVJH8Nw@mail.gmail.com>



On 05/31/2017 09:57 AM, CoolCold wrote:
> Hello!
> thanks for reply, tried to answer questions below and with help of
> gists of github as Gmail forcibly cuts the lines.
> https://gist.github.com/CoolCold/676a6f9df0478c1c2d8ac8f3e6f9e22a
>
> Added vmstat output as well.

[...]

> Sorry, but doesn't that say 95.3% idle?
> No, it says 95.3 busy with right formatting, see
> https://gist.github.com/CoolCold/676a6f9df0478c1c2d8ac8f3e6f9e22a#file-gistfile1-txt-L49

Look at the vmstat output.

procs -----------memory---------- ---swap-- -----io---- -system-- 
------cpu-----
  r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy 
id wa st
  3  0      0 130058176   2412 500660    0    0     0     0    3 17  0  
2 98  0  0
  1  0      0 130057352   2412 501012    0    0     0     0 28827 69339  
0  3 97  0  0

3rd from right is % idle.

This is 95-98% idle.  Is the rebuild done?

You are doing about 29k interrupts per second, and about 69k context 
switches.  Not heavily loaded unless this is a lower end CPU/desktop system.

This isn't a CPU bound problem if the rebuild is not done.  You'll need 
to look elsewhere.

How are the drives connected to the HBA, which HBA are you using, and 
what driver for it?  Also

     cat /proc/interrupts | grep $HBA

for the driver named $HBA (your driver),  could be helpful here ... 
though ... since you aren't throwing interrupts hard, chances are that 
this won't be as useful.

Likely ... lower end SATA HBA or motherboard based unit, or a weak expander.

--
e: joe.landman@gmail.com
t: @hpcjoe
w: https://scalability.org
g: https://github.com/joelandman



  reply	other threads:[~2017-05-31 14:07 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 [this message]
2017-05-31 14:18       ` Roman Mamedov
2017-05-31 14:35         ` Joe Landman
2017-05-31 14:14 ` Roman Mamedov
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=87cf573c-775c-ee32-1beb-d45702434366@gmail.com \
    --to=joe.landman@gmail.com \
    --cc=coolthecold@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mailinglists@websitemanagers.com.au \
    /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