…=4G innodb_file_per_table innodb_stats_on_metadata=off innodb_file_format=barracuda innodb_log_buffer_size=32M innodb_buffer_pool_instances=16 metadata_locks… tmpdir=/dev/shm innodb_undo_logs=32 innodb_old_blocks_time=0 table_open_cache=2048 table_definition_cache=16384 innodb_flush_method=O…
Post: ZFS on Linux and MySQL
May 24, 2013 By 17 Comments
… best with InnoDB, with MyISAM you’ll have to start the snapshot while holding a “flush tables with read lock” and the flush operation… ray flip a bit on a drive, instead of crashing InnoDB, it will be caught by ZFS and the data will…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
… port=3306 innodb_buffer_pool_size = 30G innodb_flush_method = O_DIRECT innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_flush_log_at… loose-innodb_flush_neighbors=0 loose-metadata_locks_hash_instances=256 innodb_buffer_pool_instances=16 # MySQL 5.5 and 5.6 loose-innodb_io…
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
… can obviously relax that by simply not fsyncing every transaction (innodb_flush_log_at_trx_commit != 1), or work around it with… will take the 1 RTT). The other transactions will lock wait until the lock(s) they need are available. The application just… your hotspots were really bad in standalone Innodb, you might consider relaxing the fsync: set innodb_flush_log_at_trx_commit to something…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… statements on an existing table could wait on a metadata lock instead of failing or returning immediately if there is a… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the… fix for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262 (Alexey Kopytov). When mysqldump was used with –innodb-optimize-keys and…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
… statements on an existing table could wait on a metadata lock instead of failing or returning immediately if there is a… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the… fix for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262 (Alexey Kopytov). When mysqldump was used with –innodb-optimize-keys and…
Post: Percona XtraBackup 2.0.7 for MySQL available for download
May 6, 2013 By 1 Comment
… pool dump files). Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with… all InnoDB error or diagnostic messages are never printed by xtrabackup_56. Bug fixed #1169971. innobackupex would still run with FLUSH TABLES WITH READ LOCK even if xtrabackup would fail when copying logs. Fixed…
Post: Percona XtraBackup 2.1.0 'release candidate' for MySQL available for download
May 7, 2013 By Leave a Comment
… pool dump files). Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with… all InnoDB error or diagnostic messages are never printed by xtrabackup_56. Bug fixed #1169971. innobackupex would still run with FLUSH TABLES WITH READ LOCK even if xtrabackup would fail when copying logs. Fixed…
Post: SHOW INNODB STATUS walk through
July 17, 2006 By 40 Comments
…) and number of tables locked by transactions. Innodb does not lock tables for normal operation so number of tables locked normally stays 0, unless… depending on your innodb_flush_log_at_trx_commit value your log writes may be more or less expensive. If innodb_flush_logs_at… IO submited by Innodb – pages to be flushed via LRU pages – dirty pages which were not accessed long time, flush list – old pages…
Post: Heikki Tuuri Innodb answers - Part I
October 26, 2007 By 19 Comments
… isolation level READ COMMITTED, then InnoDB normally does not lock the ‘gaps’, and it does not lock rows whose latest committed version does… Innodb fuzzy checkpointing is activated HT: InnoDB flushes about 128 dirty pages per flush. That means that under a heavy write load, a new flush…
