IOMeter v2006.07.27 – IOps
Iometer is an I/O subsystem measurement and characterization tool for single and clustered systems. It was originally developed by the Intel Corporation and announced at the Intel Developers Forum (IDF) on February 17, 1998 – since then it got wide spread within the industry.
Meanwhile Intel has discontinued to work on Iometer and it was given to the Open Source Development Lab (OSDL). In November 2001, a project was registered at SourceForge.net and an initial drop was provided. Since the relaunch in February 2003, the project is driven by an international group of individuals who are continuesly improving, porting and extend the product.
This mixed workload testing is what shows the true colors of a given controller’s firmware optimizations, and the 520 did not disappoint. We see it outperform *all* other SandForce models across the board. While this was enough to outmaneuver even the OCZ Octane in higher QD regions of the File and Web Server tests, the lower regions show there is only so much you can do with a given controller design. SandForce is known to have a longer data pipeline, meaning that at lower queue depths it sees longer effective latency in handling each transaction. This causes it to fall prey to the Indilinx Everest driven Octane. Even the 320 Series wins at the lowest QD figures, and it does so with half the available bandwidth (3Gb/sec)!
Light desktop usage sees QD figures between 1 and 4. Heavy / power user loads run at 8 and higher. Most SSD’s are not capable of effectively handling anything higher than QD=32, which explains the plateaus.