Originally posted by: jgold03
No slower than a RAID1+0; the data still has to be written to two disks in either setup
Actually, because you can read/write to two disks in parallel, it IS faster.
You can do multiple writes in parallel on RAID5, as long as they don't share data or parity disks (and you can do multiple reads in parallel as long as they don't share data disks). With a 4-disk RAID5 it's impossible to get more than 2 writes in parallel (and often you will only be able to get one), but you could get 3 or 4 parallel writes with an 8-disk RAID5.
With a RAID1+0, what you normally have is a RAID1 of two RAID0 arrays. With four disks, at most you can get two writes in parallel (since each write has to be done to both sides of the RAID1), although unlike the RAID5, you *always* get two writes in parallel, no matter where on the disk the data lies. The difference in throughput is generally not going to be *that* great, and you get a lot less storage with the RAID1+0 (2/3 the space in a 4-disk setup, and just over half the space in an 8-disk array).
If you know your workload is going to be write-heavy, and you can tolerate the reduced amount of available space, a RAID1+0 *will* be faster, but probably not dramatically so. Another thing to consider is that RAID5 also introduces extra system overhead unless you have a controller with onboard cache memory and hardware XOR processing.
What File Sharing Utility (other than Windows File Sharing) would you use if you had a lot more users?
I'd consider going to Linux and running some sort of Samba implementation if you want to serve a lot of Windows hosts (more than 5-10), or using Windows Server. The basic filesharing built into WindowsXP/2K starts to bog down the CPU with a lot of parallel users, especially if they're doing a lot of nonlinear operations. But if you're just using it as storage, or for streaming media, basic Windows File Sharing could handle quite a few clients (20-30, maybe more on a multiprocessor?)