… can cause downward spikes in performance. Other then that, I have also disabled query cache to avoid contention caused by query cache on…” on the y-axis. The reason why I have chosen to show “millions of rows” on the x-axis so that we can see… for those applications that are write mostly or that rely a lot on write performance, reducing the no. of secondary indexes or…

@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

I think I can explain the performance you are seeing. But first I‘d like …full, making the database a total of, say, 4 times bigger. So around 300M or 400M rows, I…80%93-the-wait-is-over/) on a newer version of iiBench showed that… matches my prediction that at 400M rows and 55GB RAM, Inno would hit a …

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.

… requirements are not that 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_commit=1, because IO times on EBS are not very…