From: Bill Davidsen <davidsen@tmr.com>
To: Kevin Ross <kevin@familyross.net>
Cc: Grant Coady <gcoady.lk@gmail.com>,
Linux RAID <linux-raid@vger.kernel.org>,
Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RAID extremely slow
Date: Tue, 31 Jul 2012 23:16:24 -0400 [thread overview]
Message-ID: <50189F88.9020805@tmr.com> (raw)
In-Reply-To: <5013A41E.5070500@familyross.net>
Kevin Ross wrote:
> On 07/27/2012 09:45 PM, Grant Coady wrote:
>> On Fri, 27 Jul 2012 14:45:18 -0700, you wrote:
>>
>>> On 07/27/2012 12:08 PM, Bill Davidsen wrote:
>>>> Have you set the io scheduler to deadline on all members of the array?
>>>> That's kind of "job one" on older kernels.
>>>>
>>> I have not, thanks for the tip, I'll look into that now.
>> Plus I disable the on-drive queuing (NCQ) during startup, right now
>> I don't have benchmarks to show the difference. This on a six by 1TB
>> drive RAID6 array I built over a year ago on Slackware64-13.37:
>>
>> # cat /etc/rc.d/rc.local
>> ...
>> # turn off NCQ on the RAID drives by adjusting queue depth to 1
>> n=1
>> echo "rc.local: Disable RAID drives' NCQ"
>> for d in a b c d e f
>> do
>> echo " set NCQ depth to $n on sd${d}"
>> echo $n> /sys/block/sd${d}/device/queue_depth
>> done
>> ...
>>
>> Maybe you could try that? See if it makes a difference. My drives
>> are Seagate.
>>
>> Grant.
>>
>
> Does disabling NCQ improve performance?
Does for me!
>
> The suggestion to use kernel 3.4.6 has been working quite well so far,
> hopefully that fixes the problem. I'll know for sure in a few more days...
>
> Thanks!
> -- Kevin
>
--
Bill Davidsen <davidsen@tmr.com>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
next prev parent reply other threads:[~2012-08-01 3:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 22:52 RAID extremely slow Kevin Ross
2012-07-26 1:00 ` Phil Turmel
2012-07-26 1:55 ` Kevin Ross
2012-07-26 2:09 ` CoolCold
2012-07-26 2:18 ` Kevin Ross
2012-07-26 5:00 ` Kevin Ross
2012-07-26 22:36 ` Kevin Ross
2012-07-27 19:08 ` Bill Davidsen
2012-07-27 21:45 ` Kevin Ross
2012-07-28 4:45 ` Grant Coady
2012-07-28 8:34 ` Kevin Ross
2012-08-01 3:16 ` Bill Davidsen [this message]
2012-07-27 2:15 ` David Dillow
2012-07-27 2:17 ` David Dillow
2012-07-27 2:17 ` Kevin Ross
2012-07-27 2:27 ` David Dillow
2012-07-27 2:53 ` Kevin Ross
2012-07-27 3:17 ` Kevin Ross
2012-08-17 21:55 ` Jan Engelhardt
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=50189F88.9020805@tmr.com \
--to=davidsen@tmr.com \
--cc=gcoady.lk@gmail.com \
--cc=kevin@familyross.net \
--cc=linux-kernel@vger.kernel.org \
--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