The array immediately fails and the N5200 Pro starts beeping like. To break the array I simply pulled out a drive. Since rebuilding an array causes quite a lot of load on the system I used this moment to see how much of a performance hit there is. Accessing the data usually isn't much of an issue, performance may suffer though.
Performance under loadEven though a failing array can be rebuilt, you still want to access your data during the rebuilding process. However, the performance we see here is something every regular user could expect, which in my opinion is more relevant. That's why I ran the test multiple times, the result did improve noticeably and I can conclude that performance is good here.Įven though performance overall is already quite good, different drives and further optimizations could probably further improve performance. Upload seemed rather slow via FTP at the first run. As you can see FTP downloads are slightly slower than the ATTO results, however still very nice.
I put a nice 350 MB movie on the N5200 Pro to test FTP speeds. Rerunning the test didn't change anything. It is however weird that download is slower than upload, I expected this to be the other way around. However, performance gets quite impressive with larger sets of data.
To test performance two tools are utilized: ATTO for Windows file sharing (by mounting a network drive) and the default command-line FTP client to test FTP.Īs with most storage devices small transfers go terribly slow. Storage is three 36 GB 10K Cheetahs in RAID 0 on a U320 LSI MegaRAID to prevent any local bottlenecks. Test setupThe N5200 Pro is connected directly to an ASUS Z7S motherboard using a factory made CAT6 cable, apart from jumbo frames, configuration is left at default.