… returned if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning …Bug fixed #1185040. The INNODB_CHANGED_PAGES table couldn’t be queried if the log tracker wasn’t … to expand too fast around 500KB tablespace size. Bug fixed #1169494. Fixed the RPM package dependencies…
Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL
June 10, 2013 By 3 Comments
… fixed #1003776. XtraDB changed page tracking used to hold the log system mutex for the log reads needlessly, …now returned if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning …size bitmap file at the right moment would make server stop with an I/O error if changed …
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
…size = 4G innodb_file_per_table = 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…
Post: How to change innodb_log_file_size safely
July 9, 2011 By 17 Comments
… 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 will…
Post: Choosing proper innodb_log_file_size
July 3, 2006 By 12 Comments
… on recovery and why large innodb_log_file_size slows down recovery. During startup after crash Innodb scans log files to find log records which only have been…, but changes from which already made it to the database. Unlike “redo” phase “undo” phase can’t be reduced by sizing your log files…
Post: Effect from innodb log block size 4096 bytes
January 3, 2011 By 19 Comments
… will use its own block size.. – Of course the things may change if “innodb_flush_log_at_trx_commit=1″…size=26G innodb_data_file_path=ibdata1:10M:autoextend 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…
Post: InnoDB Flushing: Theory and solutions
April 4, 2011 By 23 Comments
… most important parameters for InnoDB performance are innodb_buffer_pool_size and innodb_log_file_size. InnoDB works with data in memory, and all changes to data are performed… about 7/8 of innodb_log_file_size, and the “async” point is at about 6/8 = 3/4 of innodb_log_file_size. So, there is one…
Post: How to estimate time it takes Innodb to Recover ?
May 9, 2007 By 7 Comments
… if logs are of reasonable size and wikipedia has 40 minutes or so with innodb_log_file_size=256MB. In other cases I know same log file time… changes in the buffer pool. Such process means the following variables are important. Checkpointing interval This is mainly controlled by size of log files…
Post: How innodb_open_files affects performance
November 18, 2009 By 4 Comments
… open files and applying logs took about 9 minutes in this setup. This number of course can change a lot depending on hardware log file size workload and even when crash happen (how many unflushed changes we had) Repeating test with innodb_open_files…
Post: Review of MySQL 5.6 Defaults Changes
October 8, 2012 By 10 Comments
… default at 2000 ? innodb_file_per_table =1 Great! We found it is better choice in 95%+ of installations innodb_log_file_size = 48M This is still too small for any real load but a lot better than 5MB. Good to see innodb log re-sizing… I’ve been recommending for a while. innodb_stats_on_metadata = off Yet another change I actively recommended max_connect_errors = 100…
