It will depend on the stripe size you chose when you made the array. Smaller stripes are faster for windows.
Usually 32K is the best stripe size for a compromise between windows and games.
Explanation: When using a RAID0, and file smaller than the stripe size will NOT be put on both disks - it will instead be only placed on one disk and accessed. This obviously negates the benefit of RAID0. Most windows files are tiny - e.g. .ini's, .sys, .dll and others. Most RAID controllers default to a 128K or 64K stripe size which means a lot of windows files are left out - hence windows runs faster on smaller stripe RAID arrays.
Why not use 16K or 8K? Because these are so small, the larger files on the disk are broken down into so many pieces that it uses more CPU power to reconstruct the data as the calculations will normally be offloaded to the CPU.
Most game files are very large - i.e. 500MB - 1GB in size (e.g. Steam .gcf files). Now these get broken into thousands, if not millions of pieces so the CPU usage goes much higher with this. Normally I saw about 8-10% CPU utilisation on my 16K array and only 5-6% on 32K.
Generally people use 32K for the balance. 32K will have half the number of pieces of 16K so there is obvious benefit.
crud.
