From: Jason Keltz <jas@cse.yorku.ca>
To: linux-raid@vger.kernel.org
Subject: Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
Date: Mon, 20 Oct 2014 17:07:38 -0400 [thread overview]
Message-ID: <5445799A.8020205@cse.yorku.ca> (raw)
In-Reply-To: <5445361E.3010503@cse.yorku.ca>
On 10/20/2014 12:19 PM, Jason Keltz wrote:
> Hi.
>
> I'm creating a 22 x 2 TB SATA disk MD RAID10 on a new RHEL6 system.
> I've experimented with setting "speed_limit_min" and "speed_limit_max"
> kernel variables so that I get the best balance of performance during
> a RAID rebuild of one of the RAID1 pairs. If, for example, I set
> speed_limit_min AND speed_limit_max to 80000 then fail a disk when
> there is no other disk activity, then I do get a rebuild rate of
> around 80 MB/s. However, if I then start up a write intensive
> operation on the MD array (eg. a dd, or a mkfs on an LVM logical
> volume that is created on that MD), then, my write operation seems to
> get "full power", and my rebuild drops to around 25 MB/s. This means
> that the rebuild of my RAID10 disk is going to take a huge amount of
> time (>12 hours!!!). When I set speed_limit_min and speed_limit_max to
> the same value, am I not guaranteeing the rebuild speed? Is this a bug
> that I should be reporting to Red Hat, or a "feature"?
>
> Thanks in advance for any help that you can provide...
>
> Jason.
I would like to add that I downloaded the latest version of Ubuntu, and
am running it on the same server with the same MD.
When I set speed_limit_min and speed_limit_max to 80000, I was able to
start two large dds on the md array, and the rebuild stuck at around 71
MB/s, which is close enough. This leads me to believe that the problem
above is probably a RHEL6 issue. However, after I stopped the two dd
operations, and raised both speed_limit_min and speed_limit_max to
120000, the rebuild stayed between 71-73 Mb/s for more than 10 minutes
.. now it seems to be at 100 MB/s... but doesn't seem to get any higher
(even though I had 120 MB/s and above on the RHEL system without any
load)... Hmm.
Jason.
next prev parent reply other threads:[~2014-10-20 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5445332B.9060009@cse.yorku.ca>
2014-10-20 16:19 ` question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set Jason Keltz
2014-10-20 21:07 ` Jason Keltz [this message]
2014-10-28 22:38 ` NeilBrown
2014-10-29 2:34 ` Jason Keltz
2014-10-29 2:57 ` NeilBrown
2014-10-29 20:56 ` Jason Keltz
2014-10-31 19:44 ` Peter Grandi
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=5445799A.8020205@cse.yorku.ca \
--to=jas@cse.yorku.ca \
--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).