Here you can see the same in numbers. If you look at the 'ending transfer rate', you will see that the bandwidth is directly proportional to the number of drives in the array. The 'beginning transfer rate' however shows that the stripe of three and four is cut off.
This graph should show how much of the possible bandwidth is indeed cut off by FastTrak66. The stripe of two hard drives delivers exactly as we expect it. The stripe of three loses some 8 MB/s in the first three zones of the hard drives. Striping four fast drives creates a loss of some hefty 20+ MB/s in bandwidth over the first 7 zones though. Only the last 4 zones are represented properly.
This strange behavior is most likely caused by bandwidth problems within FastTrak66. The controller is simply not able to transfer data that fast. The other possible explanation could be the PCI-bus. 133 MB/s are an ideal mark that can only be reached if no other device is using the PCI bus. However, this does not explain the loss in case of the stripe of three, since FastTrak66 is obviously able to transfer more than 61 MB/s once you are using four drives.
- RAID 0 - Striping
- Make Your Own FastTrak66 Out Of An Ultra66
- The Changing Procedure
- Installation And Handling, Continued
- FastTrak Driver And Utilities
- FastTrak Driver And Utilities, Continued
- Drive Failure In RAID 1 Or RAID 0,1 Situations
- Drive Failure In RAID 1 Or RAID 0,1 Situations, Continued
- RAID 0 - What Performance Gain Can We Expect?
- The Benchmark Setup
- The Benchmark Results - Transfer Rate Of ATA Stripe Sets
- The Benchmark Results - Transfer Rate Of ATA Stripe Sets, Continued
- The Benchmark Results - Transfer Rate Of Spanning
- The Benchmark Results - Winbench Disk Winmarks
- The Benchmark Results - BAPCo Sysmark2000
- Special Problem - FDISK On Arrays Larger Than 64 GB