… – innodb_open_files which defines how many files Innodb will keep open while working in innodb_file_per_table mode. Unlike MyISAM Innodb does not have to keep open file descriptor… test with innodb_open_files=16384 I got about same crash recovery speed though with no warnings. So it looks like innodb_open_files_limit=300…
Post: Ultimate MySQL variable and status reference list
January 8, 2011 By 4 Comments
…innodb_max_purge_lagblogpercona.commanual innodb_mirrored_log_groupsblogpercona.commanual innodb_old_blocks_pctblogpercona.commanual innodb_old_blocks_timeblogpercona.commanual innodb_open_filesblogpercona.commanual Innodb…
Comment: table_cache negative scalability
April 14, 2010 By 23 Comments
… innodb_log_buffer_size = 8M innodb_additional_mem_pool_size = 8M innodb_log_file_size = 256M innodb_log_files_in_group = 2 innodb_thread_concurrency = 16 innodb_open_files = 20000 innodb_flush_method = O_DIRECT innodb…
Comment: table_cache negative scalability
April 14, 2010 By 23 Comments
… innodb_log_buffer_size = 8M innodb_additional_mem_pool_size = 8M innodb_log_file_size = 256M innodb_log_files_in_group = 2 innodb_thread_concurrency = 16 innodb_open_files = 20000 innodb_flush_method = O_DIRECT innodb…
Post: A quest for the full InnoDB status
October 31, 2008 By 4 Comments
… discovered that InnoDB will still create the status file on disk even if you do not specify innodb-status-file option. The file is actually used for every SHOW ENGINE InnoDB STATUS call, so whenever someone runs the command, InnoDB writes…-closed files (file is physically removed only after it is no longer open by any process). First be sure to run SHOW ENGINE InnoDB…
Post: Shard-Query EC2 images available
May 11, 2011 By 2 Comments
… innodb-log-buffer-size=32M innodb-log-file-size=128M innodb-open-files=1000 innodb_fast_checksum innodb-purge-threads=1 innodb-read-ahead=linear innodb-read-ahead-threshold=8 innodb-read-io-threads=16 innodb…
Post: table_cache negative scalability
November 16, 2009 By 23 Comments
… significantly larger table_cache=16384 (and appropriately adjusted number of open files) the same operation takes 660 seconds which is 151 tables… problems. Interesting enough Innodb has a very similar task of managing its own cache of file descriptors (set by innodb_open_files) As the time…
Post: Recovering CREATE TABLE statement from .frm file
December 17, 2008 By 4 Comments
… [ERROR] Cannot find or open table test/test_innodb from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another…
Post: What is the longest part of Innodb Recovery Process ?
December 20, 2007 By 2 Comments
… tables using innodb_file_per_table so “InnoDB: Reading tablespace information from the .ibd files…” stage was taking most of the time. Happily Innodb only needs to scan .ibd files when… in normal restarts as well – “Opening Tables”. As Innodb has to recompute the stats first time it opens the table this can take…
Post: How to recover deleted rows from an InnoDB Tablespace
February 20, 2012 By 3 Comments
…| +————+ | Compact | +————+ ~/recovery-tool# ./page_parser -5 -f data/salaries.ibd Opening file: data/salaries.ibd: [...] 71.43% done. 2012-02-14 …the error log. mysql (employees) > CREATE TABLE innodb_table_monitor (id int) ENGINE=InnoDB; TABLE: name employees/salaries, id 18, flags …
