…-logs to ensure that all transactions are also captured. The –apply-logs phase simply utilizes the built in crash recovery and applies the redo-logs… FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA=’orig’ AND ENGINE=’InnoDB‘; EOF mysql -N -B <<'EOF' > import-ddl.sql SELECT CONCAT…
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
June 3, 2013 By 3 Comments
… ported features can be seen in Percona Server 5.6.11-60.3 release notes. Bugs Fixed: Transaction objects are now allocated calling calloc() directly instead of using InnoDB heap allocation. This may improve… be queried if the log tracker wasn’t running. Bug fixed #1185304. Fixed the upstream bug #68970 that, in Percona Server, would…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
…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_in…
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
… the transaction commits and that takes an fsync to the redo log by default, so applying Callaghan’s law to single-server Innodb… You can obviously relax that by simply not fsyncing every transaction (innodb_flush_log_at_trx_commit != 1), or work around it with… comes from!). The least amount of data we can change in Innodb at a time is a single row, so the most…
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
…please note the transaction produces 4 INSERTs and workload is very write intensive. So what are results in this case: InnoDB gradually … 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_…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
…transaction that executed a query which opened that table. Bug fixed #1127008 (Sergei Glushchenko). Fix for bug #1070856 introduced a regression in…in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
…transaction that executed a query which opened that table. Bug fixed #1127008 (Sergei Glushchenko). Fix for bug #1070856 introduced a regression in…in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In…
Post: Percona XtraBackup 2.0.7 for MySQL available for download
May 6, 2013 By 1 Comment
… files). Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with MySQL 5.6… the log records in the transactional log being overwritten before they are copied by the log copying thread. Percona XtraBackup now stores the GTID value in…
Post: Percona XtraBackup 2.1.0 'release candidate' for MySQL available for download
May 7, 2013 By Leave a Comment
… files). Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with MySQL 5.6… the log records in the transactional log being overwritten before they are copied by the log copying thread. Percona XtraBackup now stores the GTID value in…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
…graph. We see the exact same pattern when looking at transaction latency; the baseline numbers are roughly identical for all …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_fast_shutdown…
