What are you using the Raid0 setup for?
From Computerweekly:
For example, if your business works with lots of video or large image files, you will want to ensure maximum throughput. That means you will need to spread data across individual drives as much as possible. For this use case smaller RAID chunk sizes (for example, 512 bytes -- one block -- to 8 KB) fit the bill because you want to take data from one drive while the others seek the next chunks to be read.
At the other extreme in terms of use cases would be running a database in which the amount of data read on each operation is small, say, up to 4 KB. Here you want a single I/O to be dealt with by one drive with one seek action rather than be spilt between more than one drive and multiple seeks. So, for use cases such as databases and email servers, you should go for a bigger RAID chunk size, say, 64 KB or larger.
From Toms Hardware:
If you access tons of small files, a smaller stripe size like 16K or 32K is recommended. For primarily large, sequential accesses like video files, a higher stripe size like 128K is recommended. If you're not doing either one of these, then a good overall size for many applications is 64K.
The block size would refer to what sector size the RAID controller abstracts to the computer. In virtually all cases, this is 512 bytes and is not changeable. Although, I have seen some high-end SAN units that can alter the block size, although this technique is incompatible with all versions of Windows except Vista.
