IOMeter is based on a client–server model, where one instance of the Iometer graphical user interface is managing multiple 'workers' (each one representing a separate Dynamo.exe process) which are doing the I/O. Iometer performs Asynchronous I/O - accessing files or block devices (later one allowing to bypass the file system buffers).
Iometer allows the configuration of disk parameters such as the 'Maximum Disk Size', 'Starting Disk Sector' and '# of Outstanding I/Os'. This allows a user to configure a test file upon which the 'Access Specifications' configure the I/O types to the file.
Iometer allows the configuration of disk parameters such as the 'Maximum Disk Size', 'Starting Disk Sector' and '# of Outstanding I/Os'. This allows a user to configure a test file upon which the 'Access Specifications' configure the I/O types to the file.
For USB Pen Drives, an IOPS test is pretty much the definition of 'unfair' as it simulates scenarios for which USB drives are not typically designed. Our test, which we put desktop storage through, uses IOMETER to perform 4K 50%/50% read/write cycles with 100% Random Distribution - reporting back on IOPS. This generally represents heavy database gruntwork, not something your average thumb drive should have to cope with.
Interestingly the Corsair Flash Voyager GS is the first thumb drive we have tested which can reach the same ballpark as a baseline mechanical HDD. It's not altogether clear why this is possible on this drive when others have struggled so mightily, but may be down to the capacity and number of IO channels in the controller for the drive. Either way, whilst it's not quite enough to have us eager to use the Voyager GS as a secondary system storage drive, it does greatly improve the drives chops as high performance in a range of likely tasks.
