The fastest (and unsafest) RAID is striping aka RAID 0.
If you are going to use that make sure you have backups.
[Edit: added stuff below]
A very brief RAID summary:
- RAID 0: Split data across several drives. FAST! If one drive fails then you lose all data.
- RAID 1: Write all data to multiple drives. Not faster when writing. Optionally faster when reading since you can read from several disks at one. You lose a lot of disk capacity (if using 2 drives one of them is a copy of the other, so two 1TB drives yield 1TB of space. If you go extra secure with three copies you have 1/3rd total usable space etc).
- RAID 10: Combine at least 4 drives in two pairs. Forming a stripe of mirrors or a mirror of stripes. Used when both speed and safety are needed. You lose half of the disk space.
- RAID 5: Ok when reading. Slower when writing. Advantage: you lose only one disk of capacity. Fine when mostly reading and storing large amounts of data. You lose 1 drive of capacity. You can lose one hard drive without losing any data.
- RAID 6: Same as RAID 5 with two drives of capacity lost. You can lose two hard drives without losing data. Maybe slower than RAID 5 when writing because of non-trivial parity calculations.
If you want maximum speed: Use SSDs and put them in a stripe. But keep backups of important data.
You should always keep backups of all data, a RAID is not a backup. Not even a RAID 6.
Could you clarify your edit? What do you mean by "reliability" - fault ride-through? Longevity? It contradicts your earlier requirement that "reliability is not the main factor". Also, can you describe which parts of the Wikipedia page for RAID that are confusing and that don't answer your question?
– sblair – 2012-06-16T04:36:32.340@sblair Done edit – Canadian Luke – 2012-06-16T07:07:22.117
http://serverfault.com/questions/339128/what-are-the-different-widely-used-raid-levels-and-when-should-i-consider-them – Zoredache – 2012-06-17T09:54:05.907
While their are differences between the various levels you can usually see a much bigger difference by simply adding more spindles and making damn sure you have a RAID controller with a largeish battery backed cache so your OS/software simply pushes writes to controller memory, and the controller can push them to disk when the I/O load permits it. – Zoredache – 2012-06-17T09:59:40.063