… 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 consistent…
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: How much memory Innodb locks really take ?
May 19, 2012 By 11 Comments
… 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
@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?
Post: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 11 Comments
… innodb_adaptive_flushing_method = estimate innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DIRECT innodb_max_dirty_pages…
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?
Comment: InnoDB's gap locks
April 13, 2012 By 14 Comments
… said, write queries behaves as if you were using READ COMMITTED in spite of your chosen transaction isolation level. So lets… | +——+——-+ 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
… transaction isolation level” Statement 2: “changing the ISOLATION to READ COMMITTED will help you to avoid all those extra locks” But if MySQL behaves as if READ COMMITTED is used regardless of which isolation level is actually chosen… ISOLATION is set to READ COMMITTED or REPEATABLE READ, MySQL would still behave as if READ COMMITTED is used according to statement…
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… two different ways: 1- Change the ISOLATION level to READ COMMITTED. In this isolation level, it is normal and expected that…
