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 14:54:28 +0000 [thread overview]
Message-ID: <4D2334A4.4040109@anonymous.org.uk> (raw)
In-Reply-To: <20110103163213.GC17455@fi.muni.cz>
On 03/01/2011 16:32, Jan Kasprzak wrote:
[...]
> My hardware is apparently able to keep all the disks busy most
> of the time (verified by running dd if=/dev/sd$i bs=1M of=/dev/null
> in parallel - iostat reports 99-100 % utilization of each disk and about
> 55 MB/s read per disk). All the disks are connected by a four-lane
> SAS controller, so the maximum theoretical throughput is 4x 3 Gbit/s
> = 12 Gbit/s = 0.5 Gbit/s per disk = 62.5 MByte/s per disk).
This is part of your limit. You're able to read from your discs at about
1320MB/s (24*55MB/s), but you're throwing the data away. Doing the
resync, you'd be reading two chunks for each one that's written, so
reading about 880MB/s and writing about 440MB/s. Modern 7200rpm discs
ought to be able to read at perhaps 125MB/s and write at over 100MB/s,
but because you're throttled by the PCIe x4 interface, you're only
getting about half of what your discs could do.
Check how fast one disc can go on its own with access to the whole PCIe
interface with a single dd invocation.
Cheers,
John.
next prev parent reply other threads:[~2011-01-04 14:54 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 [this message]
2011-01-04 16:41 ` Jan Kasprzak
2011-01-04 17:05 ` John Robinson
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=4D2334A4.4040109@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).