Martin Steigerwald <Martin@xxxxxxxxxxxx> writes: > - ioengine=libaio > - direct=1 > - and then due to direct I/O alignment requirement: bsrange=2k-16k > > So I now also fully understand that ioengine=sync just refers to the > synchronous nature of the system calls used, not on whether the I/Os are > issued synchronously via sync=1 or by circumventing the page cache via > direct=1 > > Attached are results that bring down IOPS on read drastically! I first let > sequentiell.job write out the complete 2 gb with random data and then ran > the iops.job. If you want to measure the maximum iops, then you should consider driving iodepths > 1. Assuming you are testing a sata ssd, try using a depth of 64 (twice the NCQ depth). Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
