Aaron, No particular reasons, it doesn’t matter if you have 4 1G or 2 2GB log files, as they are all concatenated together by InnoDB and written to in a circular fashion.

@Time Callaghan, I did not test with innodb_flush_log_at_trx_commit=1 because the durability requirements are not that stringent. And following is how I invoked iiBench: iibench -T $tbl_name -D iiBench -r 200000000 -M 1 -s 1000000 -t 100000 -I 1 -a -S

… first I’d like to note that this experiment isn’t really running the iiBench problem. The point of iiBench problem… to measure the cost of index maintenance. This experiment isn’t measuring the cost of index maintenance. Transaction-id is auto… new one. (If I read your graph correctly, you didn’t graph the performance on the first 100M rows). The minimum…

This benchmark doesn’t test the IO performance of EBS though as you’re not flushing to disks on each commit. What numbers do you get when you set innodb_flush_log_at_trx_commit to 1?