From: pg@lxra2.for.sabi.co.UK (Peter Grandi)
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Low resync throughput
Date: Fri, 27 Dec 2013 12:22:02 +0000 [thread overview]
Message-ID: <21181.28906.59447.146830@tree.ty.sabi.co.uk> (raw)
In-Reply-To: <52BD152C.5050301@ubuntu.com>
> I have been experimenting with setting up a raid array on 3
> new drives that are each capable of about 180 MB/s throughput.
I guess that if this a rotating disk drive "capable" is intended
here in the marketing sense of "cannot exceed". :-)
> I have tried raid5 and raid10 in both offset and far layouts
> using both 64k and 512k chunk sizes, and the resync speed
> seems to always be significantly less than the throughput of a
> single drive, even after I write 500,000 to sync_speed_max.
> The fastest of the bunch was raid10 in far mode, at ~140 MB/s,
> and the rest were around 110 MB/s.
The output of 'iostats -dx 1' might be interesting. :-)
Also as to RAID5 you might want to look at 'man mdadm' the
paragraph beginning "When creating a RAID5 array".
prev parent reply other threads:[~2013-12-27 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 5:50 Low resync throughput Phillip Susi
2013-12-27 12:22 ` Peter Grandi [this message]
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=21181.28906.59447.146830@tree.ty.sabi.co.uk \
--to=pg@lxra2.for.sabi.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.