… disabled), innodb_flush_log_at_trx_commit=1 and sync_binlog=1 or in tabular format: Threads Nofix Group Commit fix 1 21.51 21.99 2 30… Group Commit Fix in an upcoming Percona Server release. It is also interesting to see how Flash cards will handle innodb_flush_log_at_trx_commit=1…
Post: Heikki Tuuri Innodb answers - Part I
… features in MySQL 5.1 Q15: How frequently does Innodb fuzzy checkpointing is activated HT: InnoDB flushes about 128 dirty pages per flush. That means… way to get good performance is to set innodb_flush_log_at_trx_commit=2, that is, to flush the log to the disk only once per second. PZ…
Post: MySQL 5.5.8 and Percona Server: being adaptive
…-mysql, 500w (around 50GB of data) on RAID10. I used innodb_buffer_pool_size=24G, innodb_log_file_size=2000M (innodb_log_files_in_group=2), and innodb_flush_log_at_trx_commit=2…=1 innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=8M innodb_log_files_in_group=2 innodb_log_file_size=4G innodb_log_block_size=4096 innodb_thread_concurrency=0 innodb_flush_method = O_DIRECT innodb_read…
Post: MySQL 4 to MySQL 5 Upgrade performance regressions
… Disable Binary Logging This allows to get group commit back but obviously you loose point in time recovery and replication. Use innodb_flush_log_at_trx_commit=2 This is probably best solution. In many cases this would be good change to do with MySQL 4 also…
Post: Intel SSD 910 vs HDD RAID in tpcc-mysql benchmark
… that: the card of itself or MySQL internals + flushing logic. Now, all these results are received with innodb_flush_log_at_trx_commit=2, which in comments to previous post was called cheating. So I ran another round with innodb_flush_log_at_trx_commit=1 to…
Post: Effect from innodb log block size 4096 bytes
…MySQL 5.5.8 and Percona Server: being adaptive I mentioned that I used innodb-log-…innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=8M innodb_log_files_in_group=2 innodb_log_file_size=4G innodb_adaptive_checkpoint=keep_average innodb_thread_concurrency=0 innodb_flush_method = O_DIRECT innodb…
Post: MySQL 5.5.8 - in search of stability
…innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DIRECT innodb_log_buffer_size = 64M innodb_buffer_pool_size = 26G innodb_buffer_pool_instances=16 innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb…
Comment: When is it a time to upgrade memory ?
… log file size to about 25% of the buffer pool size innodb_log_group_home_dir = /mnt/log_mysql innodb_log_file_size=1G innodb_log_buffer_size=64M innodb_flush_log_at_trx_commit=2 [mysql.server] user=mysql basedir=/var/lib thread…
Post: Adaptive flushing in MySQL 5.6
…. Relevant MySQL options: innodb_file_per_table = true innodb_data_file_path = ibdata1:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 2 innodb_buffer_pool_size = 150G innodb_log_file_size = 4G innodb_log_files_in_group = 2 #####plugin options innodb_read…
Post: Disaster: MySQL 5.5 Flushing
… ~58GB. MySQL version: 5.5.16 Initial benchmark, which InnoDB configured for this hardware innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DIRECT innodb_log_buffer_size = 16M innodb_buffer_pool_size = 52G innodb_log_file_size = 1900M innodb_log_files_in_group = 2…

