From: Neil Brown <neilb@suse.de>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: Linux-Raid <linux-raid@vger.kernel.org>
Subject: Re: Awful Raid10,f2 performance
Date: Tue, 16 Dec 2008 08:38:31 +1100 [thread overview]
Message-ID: <18758.52823.375213.963854@notabene.brown> (raw)
In-Reply-To: message from Jon Nelson on Monday December 15
On Monday December 15, jnelson-linux-raid@jamponi.net wrote:
> A follow-up to an earlier post about weird slowness with RAID10,f2 and
> 3 drives. This morning's "check" operation is proceeding very slowly,
> for some reason.
>
> dstat is showing 14-15MB/s worth of read I/O (0 or negligible write
> I/O) on each of the 3 drives which comprise the raid10,f2.
>
> According to /proc/mdstat this is the current rate:
>
> [================>....] check = 82.9% (381575040/460057152)
> finish=60.6min speed=21554K/sec
>
> The sync_speed_min is 40000, sync_speed_max is 200000, and there is no
> other I/O on the system to speak of.
>
> blockdev shows:
>
> blockdev --getra /dev/sdb /dev/sdc /dev/sde
> 256
> 256
> 256
>
> I just now tried setting it to 64K (65536) on each device and that did
> not seem to make much difference.
>
> As you may recall from earlier posts, these drives are easily capable
> of twice or even three times this rate or more even at the inner
> tracks (70-80MB/s each on the outer tracks, 35-40MB/s on the inner
> tracks).
>
> What might be going on here?
If you think about exactly which blocks of which drives md will have
to read, and in which order, you will see that each drive is seeking
half the size of the disk very often. Exactly how often would depend
on chunk size and the depth of the queue in the elevator, but it would
probably read several hundred K from early in the disk, then several
hundred from half-way in, then back to start etc. This would be
expected to be slow.
NeilBrown
next prev parent reply other threads:[~2008-12-15 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 14:11 Awful Raid10,f2 performance Jon Nelson
2008-06-02 14:53 ` Tomasz Chmielewski
2008-06-02 15:09 ` Jon Nelson
2008-06-02 18:30 ` Keld Jørn Simonsen
2008-12-15 13:33 ` Jon Nelson
2008-12-15 21:38 ` Neil Brown [this message]
2008-12-16 2:47 ` Jon Nelson
2008-12-16 4:03 ` Keld Jørn Simonsen
2008-12-16 4:28 ` Jon Nelson
2008-12-16 10:10 ` Keld Jørn Simonsen
2008-12-16 15:26 ` Jon Nelson
2008-12-16 15:53 ` Jon Nelson
2008-12-16 22:01 ` Keld Jørn Simonsen
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=18758.52823.375213.963854@notabene.brown \
--to=neilb@suse.de \
--cc=jnelson-linux-raid@jamponi.net \
--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).