linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Dean S. Messing" <deanm@sharplabs.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help: very slow software RAID 5.
Date: Sat, 29 Sep 2007 10:52:38 -0400	[thread overview]
Message-ID: <46FE66B6.9080400@tmr.com> (raw)
In-Reply-To: <20070928233810.AC76C102F5B@medulla.enet.sharplabs.com>

Dean S. Messing wrote:
> Bill Davidsen wrote:
> : Dean S. Messing wrote:
> : > Again, I don't get these speeds. Seq. reads are about
> : > 170% of the average of my three physical drives if I turn up
> : > the look-ahead.  Then random access reads drops to slightly less
> : > than my slowest drive.
> : >   
> : As nearly as I can tell, Dean was talking about RAID-10 at that point (I 
> : also suggested that) which you haven't tried. 
>
> I was talking about the three drive RAID-5 on which I ran bonnie++ measurements.
> I have not (yet) tried RAID-10.
>
> : For small numbers of 
> : drives, assume the read speed will be (N - 1) * S for large sequential 
> : read, using RAID-10. Where S is the speed of a single drive. Random read 
> : depends on so many things I can't begin to quantify them in anything 
> : less than a full white paper, but for a single thread assume somewhere 
> : around S and aggregate (N - 1) * S again. Writes depend a lot on system 
> : tuning, stripe size, stripe_cache_size, chunk size, etc. Fortunately the 
> : best way to boost write speed is to have lots of memory and let the 
> : kernel buffer.
>
> How does one "let the kernel buffer"? (I have plenty of memory for
> most things.) I know about "write-back" vs. "write-through" to reduce
> the write asymmetry of RAID-5.  Is this what you mean by a kernel
> buffer?
>   

Just by having adequate memory you will get kernel buffering (unless you 
use fsync or similar), and performance goes up if you increase your 
stripe_cache_size, although you hit diminishing returns on that 
somewhere between 8-32MB.
> : Finally, when you create your ext filesystem, think of:
> :  - ext2 - no journal
> :  - noatime mounts to avoid journal writes
>   

Please try this before you reach any conclusions. Doing measurements on 
a filesystem instead of raw raid arrays adds bottlenecks.
> :  - manually make the journal file *large* to spread head motion over drives
> :  - consider moving journal file to a dedicated device (that old 20GB 
> : PATA drive?)
> :  - use the ext3 "stride" tuning stuff (I'm quantifying that in the next 
> : ten days).
> :
> : Or just make a RAID-10 "far" array and stop agonizing over this stuff, 
> : there is no config which is best for everything, you must realize "fast, 
> : cheap, reliable - pick two" is the design paradigm of RAID, and the more 
> : you optimize for one usage pattern the more you impact some other.
>
> Dean
> -
> 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
>
>   


-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  reply	other threads:[~2007-09-29 14:52 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18 23:09 Help: very slow software RAID 5 Dean S. Messing
2007-09-19  0:05 ` Justin Piszcz
2007-09-19  1:49   ` Dean S. Messing
2007-09-19  8:38     ` Justin Piszcz
2007-09-19 17:49       ` Dean S. Messing
2007-09-19 18:25         ` Justin Piszcz
2007-09-19 23:31           ` Dean S. Messing
2007-09-20  8:25             ` Justin Piszcz
2007-09-20 18:16             ` Michal Soltys
2007-09-20 19:06               ` Dean S. Messing
2007-09-20 15:33         ` Bill Davidsen
2007-09-20 18:47           ` Dean S. Messing
2007-09-20 21:08             ` Michael Tokarev
2007-09-21  0:58               ` Dean S. Messing
2007-09-21 13:00                 ` Bill Davidsen
2007-09-21 20:01                   ` Dean S. Messing
2007-09-21 20:21                   ` Dean S. Messing
2007-09-25  9:31                 ` Goswin von Brederlow
2007-09-25 18:16                   ` Dean S. Messing
2007-09-25 21:46                     ` Goswin von Brederlow
2007-09-25 23:50                       ` Dean S. Messing
2007-09-26  1:45                         ` Goswin von Brederlow
2007-09-27  6:23                           ` Dean S. Messing
2007-09-27  9:51                             ` Michal Soltys
2007-09-27 22:10                               ` Backups w/ rsync (was: Help: very slow software RAID 5.) Dean S. Messing
2007-09-28  7:57                                 ` Backups w/ rsync Michael Tokarev
2007-09-28 10:23                                   ` Goswin von Brederlow
2007-09-28 11:18                                     ` Michal Soltys
2007-09-28 12:47                                       ` Goswin von Brederlow
2007-09-28 14:17                                         ` Michal Soltys
2007-09-29  0:11                                   ` Dean S. Messing
2007-09-29  8:43                                     ` Michael Tokarev
2007-09-28 14:48                                 ` Bill Davidsen
2007-09-28 14:57                                   ` Wolfgang Denk
2007-09-28 16:50                                     ` Bill Davidsen
2007-10-01  4:45                                     ` Michal Soltys
2007-09-28 15:11                                   ` Jon Nelson
2007-09-28 16:25                                     ` Bill Davidsen
2007-09-28 16:52                                       ` Jon Nelson
2007-09-27 22:40                         ` Help: very slow software RAID 5 Bill Davidsen
2007-09-28 23:38                           ` Dean S. Messing
2007-09-29 14:52                             ` Bill Davidsen [this message]
2007-09-27 22:17                     ` Bill Davidsen
2007-09-28 23:21                       ` Dean S. Messing

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=46FE66B6.9080400@tmr.com \
    --to=davidsen@tmr.com \
    --cc=deanm@sharplabs.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).