Article View: comp.arch.storage
Article #467Re: RAID 1 or 5 ?
From: Malcolm Weir
Date: Sat, 02 Oct 1999 00:00
Date: Sat, 02 Oct 1999 00:00
53 lines
3325 bytes
3325 bytes
On Sat, 02 Oct 1999 11:50:21 +1200, Shaman <shaman@ihug.co.nz> caused to appear as if it was written: >Anyway back to the topic (RAid 1 vs 5; write performance and overall >performance for a file and print server with a hardware RAID card.) > >I was aware of the need to calculate parity during the write in RAID 5 but I >thought the ability to write a small peice of the whole file to each disk (in >RAID 5) would be more significant timewise. Writing is always problematic, but you are correct in that *reading* data written across multiple disks is pretty much always a win. >Does RAID 5 ever get better than RAID 1, as you add disks? The short answer is... "define better"! >ie RAID 1 vs a 8 Disk RAID 5 >is RAID 1 still better? As a rule of thumb, "powers of two plus one" work better, so 9 is a better number than 8. That said, if you are using a hardware controller, most of these things support mirrored & striped and/or mirrored & concatenated "RAID1" configurations. So ultimately, one can say that, for a given usable disk capacity, a configuration using RAID1 will pretty much always beat a configuration using RAID5. The justification for this is that disk array performance tends to boil down to the being limited by the single-spindle performance, i.e. the performance of the individual disk. So, for an array providing a capacity equal to "n" disks, you'll have "n+1" RAID5 disks capable of serving simultaneous read requests, and "2n" RAID1 (irrespective of whether they are mirrored & striped -- i.e. RAID0 & RAID1 -- or whether they are merely concatenated RAID1 drives). So for your typical file server, where you'll have enough requests in the queue to keep the thing busy, RAID1 will always win... The "penalty" of RAID1 comes, as with RAID5, when you're writing: the fact that the mirrored pair aren't spindle sync'ed means that one drive will generally complete before the other, and the operation can't complete until both are complete. With RAID5, best case, you're dealing with a "full stripe" write, which cannot complete until all drives complete... So RAID1 is a win here, too. >David Malc.
Technical Details
Message-ID:
<44317660D15B5313.C4F584267E291DEB.4B0C715DF9CF3F96@lp.airnews.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<7nl85m$3nn$1@newton.pacific.net.sg> <37E1425E.9F4D1F3B@t-online.de> <937569107.3977.0.nnrp-11.9e98b72c@news.demon.co.uk> <37e660eb.12904299@news.earthlink.net> <7sehd5$80a@journal.concentric.net> <37F548BD.AFB2D67@ihug.co.nz>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f4d7c,813a29bed80cb2f6 X-Google-Attributes: gidf4d7c,public X-Google-Thread: 10e1c8,813a29bed80cb2f6 X-Google-Attributes: gid10e1c8,public X-Google-Thread: 1144af,813a29bed80cb2f6 X-Google-Attributes: gid1144af,public From: malc@cwix.com (Malcolm Weir) Subject: Re: RAID 1 or 5 ? Date: 1999/10/02 Message-ID: <44317660D15B5313.C4F584267E291DEB.4B0C715DF9CF3F96@lp.airnews.net> X-Deja-AN: 531754302 Content-Transfer-Encoding: 7bit References: <7nl85m$3nn$1@newton.pacific.net.sg> <37E1425E.9F4D1F3B@t-online.de> <937569107.3977.0.nnrp-11.9e98b72c@news.demon.co.uk> <37e660eb.12904299@news.earthlink.net> <7sehd5$80a@journal.concentric.net> <37F548BD.AFB2D67@ihug.co.nz> X-Orig-Message-ID: <380d51fc.196444154@library.airnews.net> Content-Type: text/plain; charset=us-ascii NNTP-Posting-Time: Fri Oct 1 19:54:34 1999 Organization: Little to None NNTP-Proxy-Relay: library1.airnews.net Mime-Version: 1.0 Abuse-Reports-To: abuse at airmail.net to report improper postings Newsgroups: comp.arch.storage,comp.sys.ibm.pc.hardware.storage,fido.ger.storage