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: Fri, 21 Sep 2007 09:00:08 -0400 [thread overview]
Message-ID: <46F3C058.1050701@tmr.com> (raw)
In-Reply-To: <20070921005851.44E8910236D@medulla.enet.sharplabs.com>
Dean S. Messing wrote:
> Michael Tokarev writes:
> : Dean S. Messing wrote:
> : []
> : > [] That's what
> : > attracted me to RAID 0 --- which seems to have no downside EXCEPT
> : > safety :-).
> : >
> : > So I'm not sure I'll ever figure out "the right" tuning. I'm at the
> : > point of abandoning RAID entirely and just putting the three disks
> : > together as a big LV and being done with it. (I don't have quite the
> : > moxy to define a RAID 0 array underneath it. :-)
> :
> : "Putting three disks together as a big LV" - that's exactly what
> : "linear" md module.
> : It's almost as unsafe as raid0, but with
> : linear read/write speed equal to speed of single drive...
>
> I understand I only get the speed of a single drive was I was not
> aware of the safety factor. I had intended to use snapshotting off
> to a cheap USB drive each evening. Will that not keep me safe within a
> day's worth of data change? I only learned about "snapshots" yesterday.
> I'm utterly new to the disk array/LVM game.
>
But your read speed need not be limited if you tune the readahead.
There's also the question of how much transfer speed you actually
*need*. If your application is CPU-bound faster will not be the same as
"runs in less time," and random access is limited by the seek speed of
your drives, although some RAID tuning does apply to random writes.
> For that matter why not run a RAID-0 + LVM across two of the three drives
> and snapshot to the third?
>
> : Note also that the more drives you add to raid0-like config,
> : the more chances of failure you'll have - because raid0 fails
> : when ANY drive fails. Ditto - for certain extent - for linear
> : md module and for "one big LV" which is basically the same thing.
>
> I understand the probability increases for additional drives.
>
> : By the way, before abandoming "R" in "RAID", I'd check whenever
> : the resulting speed with raid5 (after at least read-ahead tuning)
> : is acceptable, and use that if yes.
>
> My problem is not quite knowing what "acceptable" is. I bought a Dell
> Precision 490 with two relatively fast SATA II drives. With RAID 0 I
> attain speeds of nearly 140 MB/s (using 2 drives) for reads and writes
> and the system is very snappy for everything, from processing 4Kx2K
> video to building a 'locate' datebase, to searching my very large mail
> archives for technical info.
>
When you process video and monitor the system with vmstat, do you see
significant iowait time? No, neither do I, with a modest readahead I am
totally CPU limited. If you are searching your mail database, if you
just use a text tool which reads everything, that's pure sequential
access. And unless you actually *use* the locate command, building that
database is just a way to beat your disks (and it's more sequential than
you would expect). You can turn it off and do your bit to avoid global
warming.
> When I see the speed loss of software RAID 5 (writes are at 55MB/s and
> random reads are at 54 MB/s) for everything but seq. reads (and that
> only if I increase read-ahead from 512 to 16384 to get read speeds of
> about 110 MB/s I lose heart, esp. since I don't know the other
> consequences of increasing read-ahead by so much.
>
Assuming that your have enough memory, there would be a small slowdown
in random reading a lot of small records. You should know what your
application would do, but that access is typical of looking things up in
a database or processing small records, like a DNS or mail server.
Numbers from bonnie or similar benchmarks are nice, but they show
details of various performance area, and if you don't match "what you
do" to "what works best" you make bad choices. In other words if your
application can only read 10MB/s the benchmark is telling you your disk
is fast enough to keep up with the CPU.
> : If no, maybe raid10 over
> : the same 3 drives will give better results.
>
> Does RAID10 work on three drives? I though one needed 4 drives,
> with striping across a pair of mirrored pairs.
No, that's 0+1, RAID-10 works across any number of drives.
Have you actually take 10-15 minutes to read "man md" and get the
overview of how RAID works, or are you reading bits and pieces about
individual features?
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-09-21 13:00 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 [this message]
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
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=46F3C058.1050701@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).