linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Dexter Filmore <Dexter.Filmore@gmx.de>, linux-raid@vger.kernel.org
Subject: Re: below 10MB/s write on raid5
Date: Tue, 12 Jun 2007 13:14:55 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706121314440.12460@p34.internal.lan> (raw)
In-Reply-To: <466ED4F6.5060204@tmr.com>



On Tue, 12 Jun 2007, Bill Davidsen wrote:

> Dexter Filmore wrote:
>> I recently upgraded my file server, yet I'm still unsatisfied with the 
>> write speed.
>> Machine now is a Athlon64 3400+ (Socket 754) equipped with 1GB of RAM.
>> The four RAID disks are attached to the board's onbaord sATA controller 
>> (Sil3114 attached via PCI)
>> Kernel is 2.6.21.1, custom on Slackware 11.0.
>> RAID is on four Samsung SpinPoint disks, has LVM, 3 volumes atop of each 
>> XFS.
>> 
>> The machine does some other work, too, but still I would have suspected to 
>> get into the 20-30MB/s area. Too much asked for?
>> 
>
> Increase your stripe cache size in /sys/block/mdX/md/stripe_cache_size. If 
> you have a chunk size of 256, try setting the cache size to 8192 and see if 
> your write performance ends up ~100MB/s or so.
>
>  echo 8192 > /sys/block/mdX/md/stripe_cache_size
>
> Where "X" is your array name, of course.
>
> Note, larger values will help more, but it's definitely diminishing returns, 
> so don't get carried away. There was a report of problems with size > 32768, 
> I don't remember the details, so I would avoid that as well.
>
> -- 
> bill davidsen <davidsen@tmr.com>
> CTO TMR Associates, Inc
> Doing interesting things with small computers since 1979
>
> -
> 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
>

I was the one who tried > 32768 it crashed the machine (on an older box).

Justin.

      reply	other threads:[~2007-06-12 17:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 12:46 below 10MB/s write on raid5 Dexter Filmore
2007-06-11 12:47 ` Justin Piszcz
2007-06-11 13:28   ` Dexter Filmore
2007-06-11 13:29     ` Justin Piszcz
2007-06-11 13:45       ` Jon Nelson
2007-06-11 13:53         ` Justin Piszcz
2007-06-11 14:06       ` Dexter Filmore
2007-06-11 14:07         ` Justin Piszcz
2007-06-11 22:24       ` Nix
2007-06-12  2:35         ` Jon Nelson
2007-06-13 23:54           ` Nix
2007-06-14  9:15             ` Michael Tokarev
2007-06-13 23:55           ` Nix
2007-06-12 17:16 ` Bill Davidsen
2007-06-12 17:14   ` Justin Piszcz [this message]

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.0706121314440.12460@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=Dexter.Filmore@gmx.de \
    --cc=davidsen@tmr.com \
    --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).