Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
So you tell us! Try it and see; you don't have data to put on the drives yet, so there's nothing to lose by wiping then a few times. Try "hardware" raid 0 and 5 if it's available, try striping in software, post benchmarks!I(illa Bee said:How is the preformence of RAID 5 Vs RAID 0?
I have 3-4 80gb drives to paly with now.. and im board...
defakto said:Raid 5 write speeds can be worse than a single drive also do to the parity checks. Raid 0 just doesn't have the same overhead as raid 5. You really need to consider what it will be used for when comparing the benifits and detriments of both.
This is mostly dependant on the bus the drives are on. Check this out:Volkum said:You can get better-than-single-drive speeds if you have a good card ($$$$) that does it's own parity checks. Software RAID-5 has terrible write speeds though.
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 1892.000 MB/sec
Not just the bus, but the drives, since I read that RAID5 wirting requires to: write, read, checksum, write.unhappy_mage said:This is mostly dependant on the bus the drives are on. Check this out:
That's on a dual p3 933. 1.9 GB/s. The array I've got is (I think) currently limited by the slow-but-supported Highpoint 1540 sata card (it's a bridged pata->sata design) I'm using; I get about 38 MB/s writes to the array. There are 3 disks on a pci bus - 133 MB/s total bandwidth. So apparently it's being limited to writing to one disk at a time - single disk benches show about 60 MB/s, so that's not a limit - for about a third of the pci bandwidth each. When I move to my faster 64/66 card (when drivers for it come out) I'll post a big thread about linux software raid and how awesome it is.Code:raid5: automatically using best checksumming function: pIII_sse pIII_sse : 1892.000 MB/sec
It depends on how well the raid is implemented. If you're writing the same chunk to all 3 drives, you can just calculate parity and write - whatever's on that block will be overwritten anyways, so it doesn't need to be read off first. However, using filesystems instead of block devices skews benchmarks in Windows' favor; it always takes *some* overhead to write to a filesystem, but that's a penalty that's almost always paid. Disk benchmarks in Windows have long bugged me - they're not testing the thing that matters: "how fast can I put files on this disk?". What they test is "how fast can I put bytes on this disk". Subtle difference, and filesystems make a lot of difference in this.drizzt81 said:Not just the bus, but the drives, since I read that RAID5 wirting requires to: write, read, checksum, write.