May 24, 2012

Post: How to calculate a good InnoDB log file size

a post a while ago about choosing a good InnoDB log file size.  Not to pick on Peter, but the post actually kind of talks about aa big log. However, most of the time when I run this calculation, I end up finding that the log file size needs to be a

Post: How to change innodb_log_file_size safely

… you 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

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

Comment: InnoDB Flushing: Theory and solutions

Nathan, There is no single rule. You may read http://www.mysqlperformanceblog.com/2008/11/21/how-to-calculate-a-good-innodb-log-file-size/ to get some ideas.

Comment: InnoDB Flushing: Theory and solutions

Nathan, There is no single rule. You may read http://www.mysqlperformanceblog.com/2008/11/21/how-to-calculate-a-good-innodb-log-file-size/ to get some ideas.

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. But… 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 simple mental calculation can then tell me how much total gain I can get from it. Queries are not just “bad” or “good

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_sizea result of how it works, instead of performing 1 random write, InnoDB will perform 8 random writes. I do not have a good

Post: SHOW INNODB STATUS walk through

INNODB STATUS output and how to use this info to improve MySQL Performance. To start with basics SHOW INNODB STATUS is command which prints out alog files. By monitoring log sequence number and value up to which logs have been flushed you can check if your innodb_log_buffer_size

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_filesto the 70% line limit. That is, to get this stable throughput, we need a total log file size

Post: A quest for the full InnoDB status

InnoDB status. Baron once wrote an article on how tofile descriptor numbers and in the 7th column there are the file sizes. This makes it obvious that InnoDB status has to be under file