We first introduced the hIOmon Disk I/O Ranger in our article, In The Lab With Seagate's Momentus XT 750 GB Hybrid HDD. The Disk I/O Ranger provides a Data Transferred/Time Index, which we'll refer to as DXTI. The DXTI is really just a high-level means for relative comparison of I/O performance, where a higher number corresponds to better performance (more data transferred and/or less response time).
The hIOmon DXTI metric is calculated by taking the observed amount of data transferred, converted from I/O operations to megabytes for scaling), and dividing by the combined sum of the observed time durations (actual response times) of the I/O operations responsible for transferring that data. You can think of it like a car's fuel economy index insofar as it conveys performance efficiency. It is comparable to more miles driven (more data transferred) for fuel used (response time taken to transfer this data). Or, similarly, the same number of miles driven (data transferred) using less fuel (lower response time).
To obtain our DXTI, we configured the Disk I/O Ranger to monitor at the physical volume level, which records activity between the volume manager and the disk class driver. Then, we created a number of different-sized folders and filled them with MP3 files in preparation for monitoring performance. Once we created the folders, we transferred them to the Vertex 4, as outlined on the preceding page.
Our first set of results is generated with Windows 7 installed on the Vertex 4, leaving 63% free space as we started the file transfers. In the chart below, the percentage of free space corresponds to what was available before we started moving files.
Our index drops by half between the first and third folders, with the reduction more pronounced as free space disappears. This again indicates lower write performance in the face of less available capacity.
Deleting the third folder and rebooting helped improve the DXTI so that, when folder four was transferred, performance improved. However, the index still fell short of our earlier results. Deleting folders one, two, and four, and then rebooting, also yielded a higher index, though it continues to lag the first two results we generated.
Deleting files rapidly allows the Vertex 4's write speeds to recover. Even after this recovery, though, write performance is influenced by the amount of available space.
Our second set of results is measured on the Vertex 4 set up as secondary storage, allowing us to start our test procedure with 100% available capacity.
As long as there's at least 50% free space available, the Vertex 4 performs optimally and recovers its performance nicely.
- OCZ Vertex 4 Write Performance, Revisited
- An Updated Test Procedure
- Firmware 184.108.40.206: hIOmon Disk I/O Ranger
- Firmware 220.127.116.11: AS SSD Compression Benchmark
- Firmware 1.5: HD Tune And hIOmon Disk I/O Ranger
- Firmware 1.5: AS SSD Compression Benchmark
- Firmware 1.5: Iometer Test File Monitoring
- Our Theory About How v.1.4 Changed Write Performance
- Firmware 1.5: Something Special For OCZ's Vertex 4