linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <Paul.Clements@SteelEye.com>
To: Farkas Levente <lfarkas@bnap.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: poor performance with raid1 / raid0
Date: Wed, 18 Jun 2003 10:59:59 -0400	[thread overview]
Message-ID: <3EF07E6F.FF55F908@SteelEye.com> (raw)
In-Reply-To: 3EF07C9C.7070802@bnap.hu

Farkas Levente wrote:
> 
> Paul Clements wrote:
> > Per Andreas Buer wrote:
> >
> >>Andrew Rechenberg <arechenberg@shermfin.com> writes:
> >>
> >>
> >>>Check /proc/sys/dev/raid/speed_limit_[min|max].  If they are set too low
> >>>then your re-mirror will behave as such.  To change just echo a new
> >>>value:
> >>>
> >>>echo 30000 > /proc/sys/dev/raid/speed_limit_min
> >>>echo 50000 > /proc/sys/dev/raid/speed_limit_max
> >>>
> >>
> >>I did so - and now:
> >>
> >>md6 : active raid1 md16[2] sdd6[0]
> >>      117185984 blocks [2/1] [U_]
> >>      [>....................]  recovery =  0.1% (229120/117185984)
> >>finish=59.5min speed=32731K/sec
> >
> >
> > That's probably because you just lowered the values. The maximum is
> > normally 100000. To check what the default values are, reboot and do:
> >
> > cat /proc/sys/dev/raid/speed_limit_*
> >
> > Then echo a _larger_ number into those files.
> >
> > There is no absolute maximum value (except maybe 2^32), so don't be
> > afraid to raise the values to 10 or 100 times what they were. That
> > should ensure that your resync speed is close to its theoretical
> > maximum.
> 
> can someone tell me what these numbers means?

I think I posted something a week or two ago that explained what these
are...


> of course my goal (as everyones) to achieve the maximum possible
> performance.

Well, this is a trade-off, that's precisely why these values are
tunables. 

These tunables govern the _resync_ speed of a raid1/5 array. They do not
control the regular I/O throughput. So what you generally want to do is
to set these values as high as possible without there being an impact on
normal I/O (or for that matter, system responsiveness on the whole)
during a resync.


> can I do any harm if I set these numbers to high?

Yes, the system might become sluggish or your regular I/O throughput to
the device might become very slow during resyncs if these values are too
high.

--
Paul

  reply	other threads:[~2003-06-18 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 12:32 poor performance with raid1 / raid0 Per Andreas Buer
2003-06-18 13:42 ` Andrew Rechenberg
2003-06-18 14:00   ` Per Andreas Buer
2003-06-18 14:39     ` Paul Clements
2003-06-18 14:52       ` Farkas Levente
2003-06-18 14:59         ` Paul Clements [this message]
2003-06-18 15:03         ` Ross Vandegrift

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=3EF07E6F.FF55F908@SteelEye.com \
    --to=paul.clements@steeleye.com \
    --cc=lfarkas@bnap.hu \
    --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).