Web-Server, File-Server and Workstation Patterns
The drives are tested under loads typical of servers and workstations. The names of the patterns are self-explanatory. The Web-Server pattern consists of reads only. The File-Server pattern has about 10% write requests. The Workstation pattern is used with the full capacity of the drive as well as with a 32GB partition. It has a larger percentage of writes and more diverse variants of disk access. The request queue is limited to 32 requests in the Workstation pattern.
Since external drives are not usually used for such purposes (people usually save copies of data to an external drive rather than use one as a computer’s main disk subsystem), we will only show you diagrams with performance ratings. This should be enough to get a general notion of the drive’s performance under such characteristic loads. For the File-Server and Web-Server patterns the performance rating is the average speed of the drive under every load. For the Workstation pattern we use the following formula:
Rating (Workstation) = Total I/O (queue=1)/1 + Total I/O (queue=2)/2 + Total I/O (queue=4)/4 + Total I/O (queue=8)/8 + Total I/O (queue=16)/16.
Well, this drive is much slower than any modern HDD from our latest reports. It can only cope with low server loads.
The Solo is hardly any good for a workstation although its results here are not downright poor. Once again we can note a performance boost when the test zone is limited to a 32GB partition.
Multithreaded Reading and Writing Patterns
The multithreaded tests simulate a situation when there are one to four clients accessing the virtual disk at the same time – the clients’ address zones do not overlap. We will discuss diagrams for a request queue of 1 as the most illustrative ones. When the queue is 2 or more requests long, the speed doesn’t depend much on the number of applications. You can also click the following links for the full results:
The interface being such a bottleneck, you might expect that there should not be any more performance hits due to the specific load. However, the multithreaded reading test shows that the drive is slower at reading multiple threads than just a single thread.
The Solo has no problems at multithreaded writing: it delivers the same speed irrespective of the number of write threads.