Our SSD-test consists of different, mostly based on Iometer synthetic test. After that we run two practice tests based on PCMark and last but not least two continuous activity tests. Our test bench is equipped with an Intel Core i3 on an ASRock Z97 Extreme 6 motherboard based on the Intel Z97 chipset, allowing us to test M.2-SSDs that have a PCIe 3.0 x4-interface. Tests are run under Windows 8.1. In Windows we use the Intel RST drivers
We use Iometer to determine the random read and write speeds with 4k data blocks. The performance with small data blocks is very important, because in Windows (and other operating systems) 4k is the most commonly used block size used for hard disks and SSDs. We run the tests with a queue depth of 1, 2, 4, 8, 16 and 32. This queue depth indicates how many simultaneous instructions are sent to the SSD. The performance at low queue depths is very important for consumer applications, and with QD32 SSDs can show off what they're capable off.
Iometer also measures the read and write speed with 1 MB data blocks. We use QD32, but here the number of parallel requests matters very little since the SSD controller is very good at distributing these over multiple SSD channels.
We also simulate the access patterns of a file server and a database server with Iometer. The database test entirely consists of random 8 kB operations, 67 percent of which is reading and 33 percent is writing. The file server tests is 80 percent reading and 20 percent writing, with the following transfer sizes: 10% 512 bytes, 5% 1 kB, 5% 2 kB, 60% 4 kB, 2% 8 kB, 4% 16 kB, 4% 32 kB and 10% 64 kB. Both the file server test and the database test are done with queue depth 1, 2, 4, 8, 16 and 32.
All Iometer tests are conducted with completely random data, so that SSD controllers using compression tricks don't have an edge. Each test runs for at least 30 seconds, which is much longer than comparable tests that are part of the various benchmark tools.
While all relevant synthetic test data can be gained using Iometer alone, we also run the popular AS SSD benchmark, which internally is also based on the performance with 4k data blocks (QD1 and QD64) and the sequential read and write performance. While it is redundant compared with the Iometer tests, AS SSD has two distinct advantages: first of all, the scores are nicely converted to a total score that provides a good impression of the general performance of an SSD. Secondly, AS SSDis easy to install on your own computer which allows you to compare scores.
Real-world benchmarks: PCMark
For consumer applications the real-world benchmarks PCMark7 and PCMar8 are much more important. PCMark7 simulates the hard disk access of actual software and indicates what the performance is in different scenarios. The total score is indicative of general use, and the subscores tell you what the speed is under different circumstances. PCMark7 uses traces based on modern software from the Windows 7 era. PCMark7 runs the traces in real-time, so performance gains you wouldn't notice in real-life you won't see here.
The latest version of PCMark7 also has something called the Raw scores. These scores exclude the idle time in the traces of the various tests, so the scores don't correlate directly to real-life performance. They do clearly show the performance differences between SSDs.
We also run PCMark8, the latest version of the benchmark, and it also uses traces- although these traces are based on modern software. PCMark8 uses traces of Adobe Photoshop, Adobe Illustrator, Adobe Indesign, Adobe After Effects, Microsoft Word, Microsoft Excel, Microsoft PowerPoint, World of Warcraft and Battlefield 3.
Continuous activity tests
We conduct two continuous activity tests in which we run a workload for 30 minutes on the SSD and measure the average performance for each minute. First we do this with the Iometer 4k random write test, and the the Iometer database simulation. Both continuous activity tests are done with QD32 and a file that takes up 75 percent of the available flash memory. More about these continuous activity tests later. For normal consumer use these results aren't very important, but for professional applications - in servers for example - these scores are essential, more so than any other benchmark results.
Consistency refers to how much the SSDs performance may fluctuate from one second to the next. In order to measure consistency, we once again run an Iometer 4k random write QD32 workload, but rather than taking a snapshot of the drive's performance each minute, we record an average for each second. Admittedly, performance consistency is mainly something that is relevant for the enterprise market. Those who put an SSD in a heavy duty database server will want to be sure that the performance of the used storage is predictable, as big ups and downs may result in erratic behaviour for certain workloads. For consumer workloads, performance consistency matters very little, although it will certainly influence the performance of SSDs when putting them in RAID 0. After all, when using a RAID 0 array, blocks of data will be written to two or more disks, which means that with regard to performance, the slowest drive (the "weakest link") will determine the overall level of performance. When one of the drives has poor performance consistency, the overall performance of a RAID 0 array will be relatively low, seeing as how the odds of one of the two drives having a performance "dip" are relatively high.
In this review we compare the Sandisk Ultra 3D and WD Blue 3D 1TB with other current SATA-SSDs.