…. This experiment isn’t measuring the cost of…a random query, assuming you can get each index query…when you get rid of the secondary keys is simply because you…With a 55GB buffer pool, we would expect the primary table to simply fit. But with… correct URL for version you used is http://tokutek….

…You can see that the buffer pool is sized at 55G and I am using…table has decreased the insert rate by 3x, and its not even consistent. While with the table having no secondary indexes, you can…

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.

Interesting results, and well presented. Would you mind sharing the command line you used for your iiBench clients? Also, did you run a test with innodb_flush_log_at_trx_commit = 1?

Justin, I would be doing another benchmark and use ‘innodb_ibuf_accel_rate’ together with tuning other IO related parameters that I can tune to good affect, and I will post my results.

@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

… stringent and I can afford to loose 1 second worth of data, hence I did not test with innodb_flush_log_at_trx_commit=1. I would also not recommend running on EBS with innodb_flush_log_at_trx…