… = 4 innodb_buffer_pool_instances = 4 innodb_adaptive_flushing = 1 innodb_adaptive_flushing_method = estimate innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DIRECT innodb_max_dirty_pages_pct = 50 innodb_io…

… not test with innodb_flush_log_at_trx_commit=1. I would also not recommend running on EBS with innodb_flush_log_at_trx…

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?

@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

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?

… accelerate the rate at which insert buffer pages are flushed to disk (innodb_ibuf_accel_rate) which might be interesting to tweak… big performance difference on insertion rate when increased insert buffer flushing was enabled (using the FB patch, not XtraDB but difference…