… m2.4xlarge instance as that’s the instance type with highest memory available, and memory is what really really matters. High-Memory… to ~9k INSERTs Per Second. Let’s take a look at the graphs have a better view of the whole picture. Note, in the above graph, we have “millions of rows” on the x…

…, and Inno starts catching up and the performance starts getting better, and then the new partition starts getting too big, so… or 400M rows, I would expect Inno starts hitting disk. Perhaps you could verify that by watching IOstat. Tim’s measurements (http…, today the challenge would be to index 10B rows, not 1B rows. And it’s still a good challenge. The URL for iibench…

Mark, Probably what you are referring to is provided by the configuration option “innodb_ibuf_accel_rate” available in Percona (as mentioned by Justin). Increasing/decreasing the value of innodb_ibuf_accel_rate, you will increase/decrease the insert buffer activity.

@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

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?