OS: Windows 2008 R2 Enterprise Edition CPU: Intel X5660 2.8GHz (6-core) Memory: 24GB Device Under Test: 350GB SLC PCIe 2.0 x8 I seem to be running into a Job IOPS limitation in Windows. When I run a deep queue (iodepth=66 for example) the IOPS seem to be pegged out around 200K. If I split the iodepth between two jobs I can get around 250K IOPS with the device I am testing which is what I would expect to see. Here is the command that I am currently using: fio --filename=\\.\PHYSICALDRIVE1 --ioengine=windowsaio --direct=1 --rw=randrw --bs=4K --rwmixread=70 --iodepth=66 --randrepeat=0 --norandommap --name=test --runtime=1000000 --time_based --group_reporting When I ran two jobs I simply added the numjobs=2 attribute in and reduced iodepth to 33. This is probably more of an enhancement request than an actual issue but having to split the queue between two jobs makes it difficult to get datapoints on even numbered queues beyond a certain point. -Keith -- 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
