… = true innodb_data_file_path = ibdata1:100M innodb_flush_method = O_DIRECT innodb_log_buffer_size = 128M innodb_flush_log_at_trx_commit = 1 innodb_log_file_size = 1G innodb_log_files_in_group = 2 innodb_purge_threads = 1 innodb_fast_shutdown = 1 #not innodb…
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
…:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 1 innodb_buffer_pool_size = 36G innodb_log_file_size = 4G innodb_log_files_in_group = 2 innodb_log_block_size=4096 #####plugin options innodb…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
…=0 innodb_data_file_path=ibdata1:100M:autoextend 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 = 2000M innodb_log_files_in_group = 2 innodb_file_per_table = true innodb…
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
… your hotspots were really bad in standalone Innodb, you might consider relaxing the fsync: set innodb_flush_log_at_trx_commit to something besides 1 and suddenly…_count where achievement = ‘killed_troll’”; } change your schema In Example 2, above, how above moving the ‘joined’ column to the users…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
… port=3306 innodb_buffer_pool_size = 30G innodb_flush_method = O_DIRECT innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size=128M innodb_max_dirty_pages_pct=80 innodb_file…
Post: SHOW INNODB STATUS walk through
July 17, 2006 By 40 Comments
… IO your log file requires. Note depending on your innodb_flush_log_at_trx_commit value your log writes may be more or less expensive. If innodb_flush_logs_at_trx_commit=2 log writes are done to OS cache, and being sequential writes these logs…
Post: How InnoDB handles REDO logging
February 3, 2011 By 19 Comments
…: innodb_flush_log_at_trx_commit = 0 /* Write log buffer to log about once a second and flush */ innodb_flush_log_at_trx_commit = 1 /* Write log buffer to log and flush to disk */ innodb_flush_log_at_trx_commit = 2 /* Write log buffer to log and flush about once per second */ (About once a second is related to the fact the flush…
Post: Heikki Tuuri Innodb answers - Part I
October 26, 2007 By 19 Comments
… Innodb fuzzy checkpointing is activated HT: InnoDB flushes about 128 dirty pages per flush. That means that under a heavy write load, a new flush… 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: Measuring the amount of writes in InnoDB redo logs
October 8, 2012 By 4 Comments
… when the log buffer is written. This is interesting. It means that the durability setting can skew the results: if innodb_flush_log_at_trx_commit is… look at an example when innodb_flush_log_at_trx_commit is set to 1 or 2 (again, thanks Alexey): Transaction 1 writes 100 bytes to the log buffer At commit, InnoDB…
Post: Effect from innodb log block size 4096 bytes
January 3, 2011 By 19 Comments
… innodb_file_per_table=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_adaptive_checkpoint=keep_average innodb_thread_concurrency=0 innodb_flush_method = O_DIRECT innodb…
