May 24, 2012

Post: How to change innodb_log_file_size safely

… need to change MySQL’s innodb_log_file_size parameter (see How to calculate a good InnoDB log file size), you can’t just change the parameter in the my.cnf file and restart the server. If you do, InnoDB

Post: How to calculate a good InnoDB log file size

to 128 for good measure. Since there are two log files by default, divide that in half, and now you can set innodb_log_file_sizecalculation, I end up finding that the log file size needs to be a lot smaller than it’s configured to

Post: InnoDB Flushing: a lot of memory and slow disk

to keep the number of dirty pages within the given innodb_max_dirty_pages_pct limit. Another possible solution would be to increase innodb_log_file_size… makes calculating how many pages we need to flush extremely hard (read “impossible”), and this is one of the reasons why innodb_adaptive_flushing…

Post: How Percona does a MySQL Performance Audit

… easy to miss, as is the absence of innodb_log_file_size. I won’t give you a full rundown over every option in the file… in the error log is interesting and needs to be investigated. You might find that there are InnoDB tables whose .frm files exist but… a query is going to be possible to improve a lot, and a simple mental calculation can then tell me how much total gain…

Post: Impact of logging on MySQL’s performance

to execute; logging every query; MySQL was run with default settings except following: [mysqld] user=root max_connections=3000 innodb_log_file_size=128M innodb_flush_logcalculated. As it is seen from the chart above the performance almost doesn’t depend on logging

Post: Tuning InnoDB Concurrency Tickets

size=24G innodb_data_file_path=ibdata1:10M:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size = 8M innodb_log_files_in_group=2 innodb_log_file_size=1900M innodb

Post: SHOW INNODB STATUS walk through

log files. By monitoring log sequence number and value up to which logs have been flushed you can check if your innodb_log_buffer_sizeto separate tablespace related IO from log related IO so you can see how much IO your log file requires. Note depending on your innodb_flush_log

Post: MySQL 5.5.8 and Percona Server: being adaptive

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_log_block_size=4096 innodb_thread_concurrency=0 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

Comment: Choosing innodb_buffer_pool_size

@sedat: If you change innodb_log_size, you’ll have to remove the old log files manually so MySQL can create new ones. See also http://www.mysqlperformanceblog.com/2008/11/21/how-to-calculate-a-good-innodb-log-file-size/comment-page-1/#comment-390952 Best regards, Jochen