According to the results, it doesn’t look like you’re using multiple threads for your fio test. You have named your fio control files using “32thread”, but the file doesn’t have “numjobs=” parameter. I suggest using numjobs=N, where N is the number of CPU cores (or hyperthreaded cores) in your system. For example, if you have a single Nehalem processor, uses “numjobs=8″ (4 cores x 2 hyperthreads).

Without using multiple threads (jobs) you won’t see the maximum performance from the ioDrive.

You should also try adding the “softrandommap=1″ parameter — without this parameter, the random map used may take a lot of RAM/CPU to maintain (to have a “perfect” random access pattern that doesn’t repeat access to any specific block).

Also, before you do any read tests, make sure you write the same amount of data to the ioDrive. If the ioDrive has a fresh “fio-format”, it will have no data, and if you read from it, it will just return zero’s without actually accessing the NAND flash. Without writing first, you could get inaccurate results.

Also, this technology is available for blade servers now from HP:
http://en.wikipedia.org/wiki/IO_Accelerator

Cheers,
John

… increase your thread count.