iSCSI To The Rescue
So it seems a fact of life that if you want the convenience of a NAS, you'll have to bite the bullet on performance unless all you deal with are Gigabyte-sized files. But, for some NASes, this might not be the case. Most RAID-class NASes have supported iSCSI for some time. iSCSI (Internet Small Computer System Interface) has been around for awhile and was developed as a SAN (Storage Area Network) protocol.
You can think of iSCSI as a way to provide computers with the illusion of large volumes of direct-attached storage, while the storage actually sits in a NAS or usually larger storage farm somewhere on the network. The QNAP diagram below illustrates the concept.
iSCSI requires an initiator on the client device that communicates with an iSCSI target running on stirage server. Initiators and targets can be hardware or software based.
Notice earlier that I said direct-attached storage. iSCSI volumes or LUNs (Logical Unit Number) created on iSCSI targets appear to an iSCSI initiator just like physical disks. This is why when you create an iSCSI LUN on a NAS and connect to it using an iSCSI initiator, you need to first format the LUN before you use it.
Just like any direct-attached storage, an iSCSI LUN can't be shared. (Yes, I know it's possible to share an iSCSI LUN under specific conditions and with filesystems designed to handle it. But generally, it is not recommended.) Just as you can't connect a hard drive to two computers at once, you can't share an iSCSI LUN.
So if you're giving up one of the main reasons to use a NAS—easily shared storage—what do you gain?
We've had iSCI write and read benchmarks as part of our tests for a few years now. But the iSCSI benchmarks run only the Windows File Copy tests, which measure only large file size performance.
That conversation I mentioned earlier made me realize that I had never run the full benchmark suite, which includes the smaller file-size NASPT tests. So that's what I did. I had a QNAP TS-469L on the bench, which turned in iSCSI write and read results of 101 MB/s and 82 MB/s using a RAID 5 volume. I then ran the entire NAS Benchmark suite and pulled the results and the normal benchmark results (using a standard SMB share) into the table below.
|Windows FileCopy Write||98.22||99.65||1%|
|Windows FileCopy Read||101.93||99.65||-2%|
iSCSI vs. SMB pserformance - QNAP TS-469L
I have to say that I was really surprised by the results! So surprised, that instead of running the iSCSI benchmarks three times, as I normally do, I ran them 10 times, which are the results posted in the table above.
The results show that for the tradeoff of somewhat lower large file copy performance, I was able to post an 82% gain in performance for the NASPT Content Creation benchmark. Office Productivity benchmark improvement was only a more modest 18%, however. I think the difference may be write caching, since the Content Creation benchmark is 95% writes. This guess is reinforced by the 1600% improvement in the NASPT Directory Copy To benchmark, which writes 236 MB consisting of 2,833 files in 44 folders to the NAS. The gain in the read direction is only 102%, i.e. a bit more than double, which is a nice improvement even if it is not as impressive.
Given its non-shared nature, iSCSI isn't going to be for everyone. And it has its limitations. Even though I was able to create an 8 TB iSCSI LUN on the QNAP, Windows 7 would only let me access 2 TB of it. I couldn't even format the remaining 6 TB into another volume.
There is also the issue of iSCSI performance. While it is generally true that iSCSI performance (using the Windows File Copy benchmark) tracks SMB-based file copy performance, it doesn't always. In the comparison chart below, you can see that the numbers for a given NAS run lower and in some cases, like the Synology DS413, significantly lower (61 MB/s vs. 114 MB/s).
iSCSI vs. File Copy Write performance - 4 bay NASes
Still, if you've been wanting to edit files directly on your NAS or just wish you could move folders back and forth a lot more quickly, you might give iSCSI a try. If you can live with iSCSI's limitations, you might find it can breathe new life into your old NAS!