… cold buffer pool. Then the query is tested again without restarting the database. The first test is described as the cold…=justin innodb_buffer_pool_size=64G innodb_log_file_size=4G innodb_file_per_table innodb_stats_on_metadata=off innodb_file_format=barracuda innodb_log_buffer_size=32M innodb_buffer…
Post: Percona Server for MySQL 5.5.31-30.3 now available
May 24, 2013 By Leave a Comment
… has introduced innodb_read_views_memory and innodb_descriptors_memory status variables in the Extended Show Engine InnoDB Status to improve InnoDB memory usage… slave was running with its binary log enabled and then restarted with the binary log disabled, Crash-Resistant Replication could overwrite…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… regression in the RPM packaging that prevented the server from restarting following an upgrade — instead, the server would remain stopped after… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the…
Post: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer
March 29, 2013 By 10 Comments
… overall warmup time when the entire cache is cleared (think restarting a memcache node). This is where a persistent cache can… code for this benchmark: // Identical config/code for memcached vs InnoDB $frontendOpts = array( ‘caching’ => true, ‘lifetime’ => 3600, ‘automatic_serialization’ => true ); $memcacheOpts…, here are the relative differences: InnoDB store operation was 280% higher (~1.73 ms/op) InnoDB fetch operation was 20% higher (~.06…
Comment: Implications of Metadata Locking Changes in MySQL 5.5
March 27, 2013 By 9 Comments
… ALTER in your test case is waiting on InnoDB row locks by setting innodb_lock_wait_timeout to 1 and then issuing…=3 for update; — session 2 set innodb_lock_wait_timeout=1; alter table t1 engine=innodb; And the alter will timeout after… following error: ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction
Comment: MySQL 5.5 and MySQL 5.6 default variable values differences
March 31, 2013 By 8 Comments
… sets them higher by default. Another minor correction: innodb_auto_extend_increment should be innodb_autoextend_increment (no space in autoextend) I… it in my.cnf which caused some trouble with a restart. 
Post: Magic Innodb Recovery self healing
May 22, 2007 By 2 Comments
… (in this particular corruption instance Innodb did not print table name in question), drop tables, restart Innodb without innodb_force_recovery and load them back. But just yesterday one of the customers told me he had Innodb magically…
Post: InnoDB's gap locks
March 27, 2012 By 15 Comments
… VALUES(26); ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction transaction2 > INSERT INTO t VALUES(29); ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction transaction2 > INSERT INTO t VALUES(23); ERROR 1205 (HY000…? Is possible to detect those gap locks using SHOW ENGINE INNODB STATUS: —TRANSACTION 72C, ACTIVE 755 sec 4 lock struct(s…
Post: ANALYZE: MyISAM vs Innodb
September 3, 2008 By 9 Comments
… Innodb as index stats are computed first time table is accessed after restart this often means “never” because MySQL servers are restarted frequently… become 15 times larger. So Innodb stats are both inexact and unstable. So restarting server with Innodb may change stats dramatically and affect…
Post: What is the longest part of Innodb Recovery Process ?
December 20, 2007 By 1 Comment
… the time. Happily Innodb only needs to scan .ibd files when it was not shut down correctly otherwise restarts would be even more painful. Even more longest phase has to do with restarts more than crash recovery as it presents in normal restarts as well – “Opening Tables”. As Innodb has to recompute…
