linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Jan Kasprzak <kas@fi.muni.cz>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-10 initial sync is CPU-limited
Date: Tue, 04 Jan 2011 17:05:34 +0000	[thread overview]
Message-ID: <4D23535E.5060607@anonymous.org.uk> (raw)
In-Reply-To: <20110104164123.GT17455@fi.muni.cz>

On 04/01/2011 16:41, Jan Kasprzak wrote:
> John Robinson wrote:
[...]
> 	Yes, I am aware of this. A single disk is able to do about
> 147 MB/s according to hdparm -t. However (a big "however"),
> my usage pattern rarely issues big/sequential requests, and for more
> random load the total throughput generated by all disks will be
> much lower and the disks themselves become the bottleneck.

Sure, but doing a resync does require huge sequential reads and writes.

> 	I have just been suriprised that for initial RAID-10 resync
> the bottleneck is in the (single) CPU.
>
> : but because you're throttled by the PCIe x4 interface, you're only
> : getting about half of what your discs could do.
>
> 	I have not talked about PCIe x4, but SAS 4-way multichannel.

My bad. Same effect in this situation though.

> Anyway, my SAS controller is connected by PCIe 2.0 x8, which equals
> to (if I read Wikipedia correctly :-) 32 Gbit/s, i.e. 2 GByte/s.
> So PCIe is not a bottleneck here. SAS is, and I am aware of that.

Which is why the the md kernel threads appear to be using 100% of CPU, 
they're blocked waiting for I/O. (And possibly RAM, per my other reply 
to this thread.)

Cheers,

John.

  reply	other threads:[~2011-01-04 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 16:32 RAID-10 initial sync is CPU-limited Jan Kasprzak
2011-01-04  5:24 ` NeilBrown
2011-01-04  8:29   ` Jan Kasprzak
2011-01-04 11:15     ` NeilBrown
2011-01-04 14:47     ` John Robinson
2011-01-04 17:13       ` Jan Kasprzak
2011-01-04 14:54 ` John Robinson
2011-01-04 16:41   ` Jan Kasprzak
2011-01-04 17:05     ` John Robinson [this message]
2011-01-04 17:17       ` Jan Kasprzak

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=4D23535E.5060607@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=kas@fi.muni.cz \
    --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).