… considering changing web-applications from VB6 to PhP/MySQL/Apache/InnoDB. Do you think you can show a program where row… the transaction is not interrupted until the transaction is finished/committed? A example of a program is worth a 1000 instructions…
Comment: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 11 Comments
… with innodb_flush_log_at_trx_commit=1. I would also not recommend running on EBS with innodb_flush_log_at_trx_commit=1…
Post: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 11 Comments
… 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…
Comment: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 11 Comments
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?
Comment: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 11 Comments
@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
Comment: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 11 Comments
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?
Comment: MySQL on Amazon RDS part 1: insert performance
April 25, 2012 By 37 Comments
I see no improvement from RDS with innodb_flush_log_at_trx_commit set to 2 or 0. My benchmarks have the same results, regardless of the setting. Does RDS fools the flush in some way or has the setting disabled somehow?
Post: InnoDB's gap locks
March 27, 2012 By 14 Comments
… | +——+ transaction2> START TRANSACTION; transaction2> INSERT INTO t VALUES(26); transaction2> COMMIT; transaction1> select * from t where i > 20 FOR UPDATE; +——+ | i… FOR UPDATE. InnoDB provides REPEATABLE READ for read-only SELECT, but it behaves as if you use READ COMMITTED for all write…
Comment: InnoDB's gap locks
April 13, 2012 By 14 Comments
… an example: “InnoDB provides REPEATABLE READ for read-only SELECT, but it behaves as if you use READ COMMITTED for all write… | +——+——-+ session2> update t set c=”baron” where i=3; session2> commit; session2> select * from t; +——+——-+ | i | c | +——+——-+ | 3 | baron | | 5 | aaron…
Comment: InnoDB's gap locks
April 4, 2012 By 14 Comments
Andy, With READ COMMITTED InnoDB doesn’t take additional locks on the gap, improving the …(26); Query OK, 1 row affected (0.00 sec) session1> commit; session2> commit; session1> select * from t; +——+ | i | +——+ | 21 | | 26 | | 30 | +——+ No…
