ioSafe 1513+ Review: A Disaster-Resistant Synology DS1513+
by Ganesh T S on August 13, 2014 7:30 AM EST- Posted in
- NAS
- Storage
- Synology
- Enterprise
- ioSafe
Single Client Performance - CIFS & NFS on Linux
A CentOS 6.2 virtual machine was used to evaluate NFS and CIFS performance of the NAS when accessed from a Linux client. We chose IOZone as the benchmark for this case. In order to standardize the testing across multiple NAS units, we mount the CIFS and NFS shares during startup with the following /etc/fstab entries.
//<NAS_IP>/PATH_TO_SMB_SHARE /PATH_TO_LOCAL_MOUNT_FOLDER cifs rw,username=guest,password= 0 0
<NAS_IP>:/PATH_TO_NFS_SHARE /PATH_TO_LOCAL_MOUNT_FOLDER nfs rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2, sec=sys,mountaddr <NAS_IP>,mountvers=3,mountproto=udp,local_lock=none,addr=<NAS_IP> 0 0
The following IOZone command was used to benchmark the CIFS share:
IOZone -aczR -g 2097152 -U /PATH_TO_LOCAL_CIFS_MOUNT -f /PATH_TO_LOCAL_CIFS_MOUNT/testfile -b <NAS_NAME>_CIFS_EXCEL_BIN.xls > <NAS_NAME>_CIFS_CSV.csv
IOZone provides benchmark numbers for a multitude of access scenarios with varying file sizes and record lengths. Some of these are very susceptible to caching effects on the client side. This is evident in some of the graphs in the gallery below.
Readers interested in the hard numbers can refer to the CSV program output here.
The NFS share was also benchmarked in a similar manner with the following command:
IOZone -aczR -g 2097152 -U /nfs_test_mount/ -f /nfs_test_mount/testfile -b <NAS_NAME>_NFS_EXCEL_BIN.xls > <NAS_NAME>_NFS_CSV.csv
The IOZone CSV output can be found here for those interested in the exact numbers.
A summary of the bandwidth numbers for various tests averaged across all file and record sizes is provided in the table below. As noted previously, some of these numbers are skewed by caching effects. A reference to the actual CSV outputs linked above make the entries affected by this effect obvious.
ioSafe 1513+ - Linux Client Performance (MBps) | ||
IOZone Test | CIFS | NFS |
Init Write | 68 | 66 |
Re-Write | 68 | 73 |
Read | 34 | 123 |
Re-Read | 35 | 123 |
Random Read | 20 | 59 |
Random Write | 62 | 73 |
Backward Read | 19 | 46 |
Record Re-Write | 38 | 1300* |
Stride Read | 31 | 105 |
File Write | 68 | 77 |
File Re-Write | 68 | 78 |
File Read | 24 | 92 |
File Re-Read | 24 | 92 |
*: Number skewed due to caching effect |
43 Comments
View All Comments
Howard - Saturday, August 16, 2014 - link
I don't know about anyone else, but the "3-2-1 rule" sounds really dumb, especially when the "1" means that you should have the data in TWO different physical locations.jaden24 - Friday, August 29, 2014 - link
But can it survive a fire, a flood, and still serve up the game Crysis?Mike Kobb - Tuesday, December 16, 2014 - link
In your closing paragraph, you comment on the fan noise as making the unit suitable for an air conditioned server room.I couldn't find any other mention of fan noise in the review. Is it significantly louder than the Synology 1513+ fans? Are they loud under all circumstances, or only when the ambient temperature is high or the unit is heavily loaded? The ioSafe web site lists a range of 25-59 db(A), which is an enormous spread.