OCZ Vertex 4 Indilinx Everest 2-Infused SSD
Test Setup, IOMeter 1.1 RC and SANDRA
Our Test Methodologies: Under each test condition, the Solid State Drives tested here were installed as secondary volumes in our testbed, with a standard spinning hard disk for the OS and benchmark installations. Out testbed's motherboard was updated with the latest BIOS available as of press time and AHCI (or RAID) mode was enabled. The SSDs were secure erased and left blank without partitions wherever possible, unless a test required them to be partitioned and formatted, as was the case with our ATTO, PCMark 7, and CrystalDiskMark benchmark tests. Windows firewall, automatic updates and screen savers were all disabled before testing. In all test runs, we rebooted the system, ensured all temp and prefetch data was purged, and waited several minutes for drive activity to settle and for the system to reach an idle state before invoking a test.
|
Motherboard - Video Card - Memory - Audio - Hard Drives -
|
Hardware Used: Intel Core i7-2600K Asus P8Z6-V Pro (Z68 Chipset, AHCI Enabled) NVIDIA GeForce GTX 285 4GB Kingston DDR3-1600 Integrated on board WD Raptor 150GB (OS Drive) Samsung SSD 830 (256GB) OCZ Vertex 3 (480GB) Corsair Force GT (240GB) Crucial M4 (256GB) OCZ Octane (512GB) Intel SSD 520 (240GB) OCZ Vertex 4 (256GB & 512GB) |
OS - Chipset Drivers - DirectX - Video Drivers - |
Relevant Software: Windows 7 Ultimate SP1 x64 Intel 9.2.0.1030, iRST 10.5.1027 DirectX 11 NVIDIA GeForce 275.33 Benchmarks Used: IOMeter 1.1.0 RC HD Tune v4.61 ATTO v2.47 AS SSD CrystalDiskMark v3.01 x64 PCMark 7 SiSoftware Sandra 2011 |
|
As we've noted in previous SSD articles, though IOMeter is clearly a well-respected industry standard drive benchmark, we're not completely comfortable with it for testing SSDs. The fact of the matter is, though our actual results with IOMeter appear to scale properly, it is debatable whether or not certain access patterns, as they are presented to and measured on an SSD, actually provide a valid example of real-world performance for the average end user. That said, we do think IOMeter is a reliable gauge for relative available throughput within a given storage solution. In addition there are certain higher-end workloads you can place on a drive with IOMeter, that you an't with most other storage benchmark tools available currently.
In the following tables, we're showing two sets of access patterns; our custom Workstation pattern, with an 8K transfer size, 80% reads (20% writes) and 80% random (20% sequential) access and IOMeter's default access pattern of 2K transfers, 67% reads (34% writes) and 100% random access.
The OCZ Vertex 4 drives performed very well, leading the other drives, when using IOMeter's default access pattern, which uses small 2K transfer size and 100% random access. With out custom access pattern that uses a somewhat larger transfer size and a mix of random and sequential access, however, the Vertex 4 drives stumble a bit and land somewhere around the middle of the pack.
In terms of total transfers, we see a similar trend. The OCZ Vertex 4 offers best of class bandwidth with the default access pattern, but middling performance with our custom test.
|
Next we ran SiSoft SANDRA, the the System ANalyzer, Diagnostic and Reporting Assistant. Here, we used the Physical Disk test suite and provided the results from our comparison SSDs. The benchmarks were run without formatting and read and write performance metrics are detailed below.
Things seemingly take a turn for the worse in the SiSoft SANDRA physical disk test. The new Vertex 4's trail the pack in terms of read bandwidth, but put up excellent write numbers. We do not, however, thing these read scores translate into a real-world performance penalty. We'll explain a little later.