… tmpdir=/dev/shm innodb_undo_logs=32 innodb_old_blocks_time=0 table_open_cache=2048 table_definition_cache=16384 innodb_flush_method=O_DIRECT key_buffer_size=10G # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0 innodb…
Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL
June 10, 2013 By 3 Comments
… if the XtraDB changed page tracking was enabled and variable innodb_flush_method was set to ALL_O_DIRECT. Bug fixed #1131949…. XtraDB changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write-intensive… enabled. Bug fixed #1184517. The INNODB_CHANGED_PAGES table couldn’t be queried if the log tracker wasn’t running. Bug fixed…
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
…:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 1 innodb_buffer_pool_size = 36G innodb_log_file_size = 4G innodb_log_files_in_group = 2 innodb_log_block…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
… = 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_in_group = 2 innodb_purge_threads = 1 innodb…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
…=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_trx_commit = 1 innodb_log_buffer_size=128M innodb_max_dirty…
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
… the redo log by default, so applying Callaghan’s law to single-server Innodb, we’d get: [On a single node Innodb server… can obviously relax that by simply not fsyncing every transaction (innodb_flush_log_at_trx_commit != 1), or work around it with by… your hotspots were really bad in standalone Innodb, you might consider relaxing the fsync: set innodb_flush_log_at_trx_commit to something besides…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
… innodb_data_file_path=ibdata1:100M:autoextend innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DIRECT innodb_log_buffer_size = 16M innodb_buffer_pool_size = 52G innodb_log_file_size = 2000M innodb_log_files…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the… 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
… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the… 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
… prevent XtraBackup failures that are caused by the log records in the transactional log being overwritten before they are copied by the… 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 by terminating xtrabackup process immediately on log copying…
