NAS Configuration

Test Setup for Single Client Tests

Our test system (client PC) for single client tests consists of the following components:

As you can see, we use a pretty strong test system with an ultra-fast PCIe SSD from which all the tests are executed to make sure there is no bottleneck on our side, since the RevoDrive 350 480 GB can achieve up to 1800 MB/s read and 1700 MB/s write speeds (sequential). We also equipped the above system with an Intel X540-T2 network adapter for up to 10GbE transfer speeds for NAS servers that feature a 10GbE Ethernet controller. The Zyxel XS1920 smart managed switch is also essential in achieving such high speeds with copper wires.

Thanks Section

Building a suitable test bed for NAS reviews is really hard and expensive; however, we were lucky enough to have the support of several companies we would like to mention and thank, one by one.

Shuttle for helping us to acquire twelve DS81 barebone slim-PCs.



OCZ for the RevoDrive 350 and dozen ARC 100 SSDs with a capacity of 240 GB each.



ZyXEL for the XS1920 10GbE Smart Managed Switch.



CyberPower Systems for kindly providing the PR2200ELCDSL UPS (Professional Tower Series).



Caseking.de for kindly providing six Intel Pentium G3260 CPUs.



Overclockers.co.uk for kindly providing six Intel Pentium G3260 CPUs.



Corsair for kindly providing the DDR3 SODIMM memory kits.

Methodology

We use two programs to evaluate the NAS server's performance. The first is custom-made. It performs ten basic file transfer tests and measures the average MB/s speed for each. To extract results that are as accurate as possible, we run all selected tests ten times and use the average as the final result.


The second program we use in our test sessions is DiskSpd by Microsoft. This is a highly flexible storage test tool capable of very accurately simulating different workloads. We wrote two advanced scripts, one that simulates an On-line Transaction Processing (OLTP) system and one that simulates an On-line Analytical Processing (OLAP) system. The OLTP scenario consists of a large number of short transactions, which has the number of IOPs (Input/Output Operations Per Second) play a key role. The number of transactions is low in our OLAP scenario, but the queries can be very complex. Response times are very importance for an OLAP system, and a NAS server's maximum throughput speed is reached in this scenario since the block size is quite large.

OLTP systems generally serve the purpose of gathering input information and storing it in a database. This is done on a very large scale, and the most common operations are INSERT, UPDATE, and DELETE. An OLTP database holds detailed, current data, and an entity model, usually 3NF, is used as the schema to store transactional databases. An OLTP database also usually has high read-to-write ratios (typically 90/10 to 70/30).

OLAP systems are used to analyze the data stored in a database. As such, OLAP systems mostly apply select operations in very large data warehouses in order to collect information (data mining). An OLAP database consists of aggregated, historical data stored in multi-dimensional schemas (usually star schemas). Their read-to-write ratio is very high, and in some cases, there might only be read operations.