… innodb_buffer_pool_size = 55G innodb_log_file_size = 1G innodb_log_files_in_group = 4 innodb_buffer_pool_instances = 4 innodb_adaptive_flushing = 1 innodb_adaptive_flushing_method = estimate innodb_flush_log_at_trx_commit = 2 innodb_flush…
Comment: Benchmarking single-row insert performance on Amazon EC2
… 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…
Comment: Benchmarking single-row insert performance on Amazon EC2
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: MySQL on Amazon RDS part 1: insert performance
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: Benchmarking single-row insert performance on Amazon EC2
@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
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: Innodb Performance Optimization Basics
…:autoextend innodb_log_group_home_dir = /usr/local/mysql/data innodb_buffer_pool_size = 2000M innodb_additional_mem_pool_size = 2M innodb_log_file_size = 65M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb…
Post: Troubleshooting MySQL Memory Usage
…: while true do date >> ps.log ps aux | grep mysqld >> ps.log sleep 60 done Check for Table…VSZ” going down. What you might see instead is flushing tables regularly or reducing table cache reduces memory…_ID: 7234 TABLE_SCHEMA: test TABLE_NAME: my ENGINE: InnoDB NAME: #sql516_1c42_2 TABLE_ROWS: 0 AVG_…
Comment: How FLUSH TABLES WITH READ LOCK works with Innodb Tables
… not having log files and data on the same partition or synchronization of binary log and innodb snapshot. In certain versions FLUSH TABLES WITH READ LOCK would not block “commit” operation which caused wrong binary log positions…
Comment: How FLUSH TABLES WITH READ LOCK works with Innodb Tables
… using FLUSH TABLES WITH READ LOCK. 1. copy meta data files, like frm file. 2. copy data files other than InnoDB. 3… hot backup, frm files are consistent. 2. we only use InnoDB as our engine, no other engines used. 3. get binlog… postion information from xtrabackup_binlog_pos_innodb file since InnoDB will wirte these information in its commit log. Am i clear and right…

