From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: stripe_cache_size and performance
Date: Tue, 26 Jun 2007 10:37:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706261036560.3561@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0706260916070.5806@gheavc.wnzcbav.cig>
On Tue, 26 Jun 2007, Jon Nelson wrote:
> On Tue, 26 Jun 2007, Justin Piszcz wrote:
>
>>
>>
>> On Tue, 26 Jun 2007, Jon Nelson wrote:
>>
>>> On Mon, 25 Jun 2007, Justin Piszcz wrote:
>>>
>>>> Neil has a patch for the bad speed.
>>>
>>> What does the patch do?
>>>
>>>> In the mean time, do this (or better to set it to 30, for instance):
>>>>
>>>> # Set minimum and maximum raid rebuild speed to 60MB/s.
>>>> echo "Setting minimum and maximum resync speed to 60 MiB/s..."
>>>> echo 60000 > /sys/block/md0/md/sync_speed_min
>>>> echo 60000 > /sys/block/md0/md/sync_speed_max
>>>
>>> sync_speed_max defaults to 200000 on this box already.
>>> I tried a binary search of values between the default (1000)
>>> and 60000 which resulted in some pretty weird behavior:
>>>
>>> at values below 26000 the rate (also confirmed via dstat output) stayed
>>> low. 2-3MB/s. At 26000 and up, the value jumped more or less instantly
>>> to 70-74MB/s. What makes 26000 special? If I set the value to 20000 why
>>> do I still get 2-3MB/s actual?
>
>
>> You want to use sync_speed_min.
>
> I forgot to say I changed the values of sync_speed_min.
>
>
> --
> Jon Nelson <jnelson-linux-raid@jamponi.net>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Sounds quite strange, what chunk size are you using for your RAID?
next prev parent reply other threads:[~2007-06-26 14:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 18:28 stripe_cache_size and performance Jon Nelson
2007-06-21 19:42 ` Raz
2007-06-21 23:09 ` Jon Nelson
2007-06-22 15:01 ` Raz
2007-06-22 15:10 ` Justin Piszcz
2007-06-25 16:48 ` Bill Davidsen
2007-06-25 17:00 ` Justin Piszcz
2007-06-25 18:20 ` Justin Piszcz
2007-06-25 18:21 ` Justin Piszcz
2007-06-25 18:42 ` Justin Piszcz
2007-06-25 19:48 ` stripe_cache_size and performance [BUG with =64kb] Justin Piszcz
2007-06-25 19:49 ` Justin Piszcz
2007-06-25 20:36 ` Justin Piszcz
2007-06-25 20:42 ` Justin Piszcz
2007-06-25 22:12 ` stripe_cache_size and performance Jon Nelson
2007-06-25 22:19 ` Dan Williams
2007-06-25 23:23 ` Jon Nelson
2007-06-25 22:21 ` Justin Piszcz
2007-06-26 13:58 ` Jon Nelson
2007-06-26 14:00 ` Justin Piszcz
2007-06-26 14:16 ` Jon Nelson
2007-06-26 14:37 ` Justin Piszcz [this message]
2007-06-26 15:22 ` Jon Nelson
2007-06-26 15:54 ` Justin Piszcz
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=Pine.LNX.4.64.0706261036560.3561@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--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).