Raid 0: Blessing or hype?
Yoeri Lauwers writes "Tweakers.net investigates matters a bit more clearly and decides that AnandTech and Storagereview should think twice before they shout that "RAID 0 is useless on the desktop". Tweakers.net's tests illustrate the contrary"
I don't care what tests people have done or what benchmarks they're spouting off, RAID 0 works.
I used to have a system which used relatively cheap 5400 RPM drives in a RAID 0 array. There was a quite noticable difference when not using RAID 0. When using 2 or 4 drives the system was damn fast even though the drives were individually slow.
I don't even read these articles. I know it makes a difference.
Sure, lose one drive and you lose everything. There are better ways to store everything on one "drive letter"
Have you tried mount points in Windows? It's Disk Manager, right click on a drive and choose "Change Drive Letter or Paths..." - although it has to be an empty partition when you do this... It's just like linking drives to mount points in *nix.
"We know what happens to people who stay in the middle of the road. They get run over." - Aneurin Bevan
Actually, it's bye bye da or bye bye ta.
A common misconception is that striping beyond 2 drives is "worthless." That simply isn't true: remember that the inside of the drives, close to the spindles, has a transfer rate that is nearly half what it is on the outside cylindars. By striping 4 drives togeather, about half the bandiwdth is wasted near the FRONT of the drive, but near the tail, it's almost all being used. The effect is that the drive feels uniformly quick no matter what part of the drive you are reading from!
I personally jumped from a single drive to a 4-drive SATA raid-0 system, composed of 120GB drives from two different manufacturers.
The system screams.
I can't tell you how nice it is to have my computer boot in half the time... how your system feels like you always wished it would feel. You can add all the memory you want, all the processing power you want, but if you can't feed the computer, it's all pointless.
The only thing I wish now was that my system had a faster and/or wider bus that would allow me to take advantage of all the currently unused bandwidth available from the four drives.
A common theme, revisited several times, in the article is that the other conclusions were wrong because they used low-load testing.
"A safe conclusion would be that a Business Winstone 2004-benchmark alone is not a good starting point when testing RAID 0 performance. On the contrary: to have some reliable tests, we will need to put heavy loads on the array."
In essence, if my understanding is correct, they're saying that the value of a RAID 0 setup is under constant extreme loads, not the loads created by business applications or games. Isn't this entirely the point of the articles in question - That given the sporatic, generally light load of even power users, RAID 0 is not really that beneficial (as random access plays even more of a part than gross throughput)?
Even under perceived heavy I/O loads, the reality is often that the hard disk is under-used - I occasionally compress videos from miniDV to DVD, and my CPU would need a four or five fold increase in speed to even begin to put pressure on the single 7200 RPM hard disk.
Of course they do. After all, they've spent extra money and time pimping out their rigs.
But for the majority of us normal people who are running huge multi-threaded database applications on their desktop machines
Sorry, most slashdotters are NOT using Longhorn yet.
Just the thought of using RAID-0 makes me shiver. The only people who should use this are people who keep good backups, and like using them. The speed gains are of little use for individuals, and for the professionals or corporations that might actually want the speed-up, the chances of data-loss are too high.
That's not to say there isn't a purpose for RAID-0 - it teaches people how useful backups are. The hard way.
Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
Just post the relevant Wiki information about Raid 0, dont need Raid's life history ;).
RAID 0
A RAID 0 Array (also known as a stripe set) splits data data evenly across two or more disks with no parity information for redundancy. RAID-0 is normally used to increase performance, although it is also a useful way to create a small number of large virtual disks out of a large number of small ones. Although RAID-0 was not specified in the original RAID paper, an idealized implementation of RAID-0 would split I/O operations into equal-sized blocks and spread them evenly across two disks. RAID-0 implementations with more than two disks are also possible, however the reliability of a given RAID-0 set is equal to the average reliability of each disk divided by the number of disks in the set. That is, reliability (MTBF) decreases linearly with the number of members - so a set of two disks is half as reliable as a single disk. The reason for this is that the file system is distributed across all disks. When a drive fails the file system cannot cope with such a large loss of data and coherency since the data is "striped" across all drives. Data can be recovered using special tools, however it will be incomplete and most likely corrupt.
RAID-0 is useful for setups such as large read-only NFS servers where mounting many disks is time-consuming or impossible and redundancy is irrelevant. Another use is where the number of disks is limited by the operating system. In Windows, the number of drive letters is limited to 24, so RAID-0 is a popular way to use more than this many disks. However, since there is no redundancy, yet data is shared between drives, hard drives cannot be swapped out as all disks are interdependant upon each other.
RAID 0 was not one of the original RAID levels.
Unlike other RAID-levels, RAID 0 does not offer protection against drive failure in any way, so it's not considered 'true' RAID by some (the 'R' in RAID stands for 'redundant', which does not apply to RAID-0).
When you have multiple hard drives, it's more likely that one will fail than if you just have one. For the obvious statistical reasons. Plus because of heat problems in many systems.
In a non-RAID setup with multiple hard drives, when one fails, you lose whatever was on that drive.
With RAID-n (for non-zero n), you lose nothing. You say "oh well", put in a spare drive, and send the old one back for replacement. (In the other order if you're cheap.) The array rebuilds itself. Without even shutting down the machine, if you have the hot-swappable drive cages.
With RAID-0, you lose everything on all of your hard drives.
RAID-0 is considerably less reliable than a single hard drive.
Since 2002, I have been using the SIIG Raid 0 http://www.siig.com/product.asp?pid=424 card on a 1999 Sawtooth G4 with 0.48TB of internal storage. Hardware-wise, this is an OEM Acard card; also available from Sonnet and Miglia.
_ RAID.html
No disk failures to date ---I backup weekly with Apple's Backup 2.0
Here are some benchmarks that compare software RAID 0 performance (included free with OS X) vs. hardware RAID 0: http://www.xlr8yourmac.com/OSX/OSX_RAIDvsIDE_Card
The next pasture is always greener
'RAID 0 (Score:0, Redundant)' LOL!
The fact that you reply anon says it all. Tweakers.net has a fine reputation among the Dutch, which is shown by the huge traffic amounts on their site (even when not being slashdotted) and their memberdatabase on both the forums and the site.
The quality of their forums and their articles are both very high, mostly concerning hardware.
The fact that this article was translated means they want to be a serious contestant in this discussion against major English sites.
Writing an article in Dutch which shows the contrairy of something said in English wouldnt be fair to those concerned, would it?
(:
Nope, reliability goes down.
Let's suppose that both the 80Gb and the 160Gb drives have a possibility of failing in a month of 10%.
Now, with the 1x160Gb you have 10% of having a failure this month, obviously. What's the probability for both drives?
Well, since each one won't fail 90% of the time, the probabilities of both not failing is 81% (0.9*0.9). The rest, 19% is the possibility that one or both fail, therefore, instead of a 10% failure rate, you get 19%... nearly twice!
A friend who works with NAS/SAN systems jokingly told me that a hard drive exists in only 2 states:
1) Failed
2) About to fail
Tb.
An OPEN mind is a beautiful thing...
1. Anandtech and StorageReview benchmarked RAID 0 and found that, for desktop applications, RAID 0 is slightly slower than a single drive, because the things that RAID 0 is good at are not the things that desktops need.
2. So we changed the benchmarks to really need the things that RAID 0 is good at.
3. And now, RAID 0 improves things!
4. Therefore, the benchmarks in #1 were wrong.
Summary of the summary:
I'm looking for my keys under this lamppost because the light is better here.