June 18, 2013

Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1

Transactions Identifiers are one of the new features regarding replication in…CHANGE MASTER TO to instruct all servers to use GTIDs Disable read-only mode This procedure will switch all your … Slave_IO_Running: No Slave_SQL_Running: Yes [...] The error log tells us why the IO thread has not started: …

Post: Percona XtraBackup 2.0.7 for MySQL available for download

… that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread. Percona XtraBackup…. Percona XtraBackup didn’t initialize per-thread data in the log copying thread which could cause XtraBackup to crash. Bug fixed… from source innodb56 target didn’t have an option to disable DTrace like innodb55 has. Fixed by adding -DENABLE_DTRACE=OFF…

Post: Virident vCache vs. FlashCache: Part 2

… the exact same pattern when looking at transaction latency; the baseline numbers are roughly identical… dirty threshold. Time-based flushing has been disabled. In this case, both systems produce better…_log_buffer_size = 128M innodb_flush_log_at_trx_commit = 1 innodb_log_file_size = 1G innodb_log

Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue

… or returning immediately if there is a transaction that executed a query which opened that …#68845 which could unnecessarily increase contention on log_sys->mutex in write-intensive workloads. Bug fixed…additional work is done when userstat is disabled. Bug fixed #1128066 (Alexey Kopytov). Other bug …

Post: Percona Server for MySQL 5.5.30-30.2 now available

… or returning immediately if there is a transaction that executed a query which opened that …#68845 which could unnecessarily increase contention on log_sys->mutex in write-intensive workloads. Bug fixed…additional work is done when userstat is disabled. Bug fixed #1128066 (Alexey Kopytov). Other bug …

Post: What is innodb_support_xa?

log is also disabled.) The prepare-then-commit process does two important things: it ensures that the binary log and the engine’s transaction log agree on which transactions are committed; and it ensures that…

Post: MySQL 4 to MySQL 5 Upgrade performance regressions

… code path if XA is disabled ? Many customers do not flush binary log anyway and use single transactional storage engine so they do… to have innodb_flush_logs_at_trx_commit=1 so transactions are truly durable. You have to have log-bin enabled to get… the processlist for multiple statement transactions. Looking at SHOW INNODB STATUS you would notice large amount of log writes and fsyncs per…

Post: New SpecJAppServer results at MySQL and Sun.

…my.cnf (included in FDA) [mysqld] sql-mode = IGNORE_SPACE transaction-isolation = READ-COMMITTED max_allowed_packet = 1M max_connections=300…are somethat benchmark optimized – for example doublewrite is disabled; checksums are disabled; binary log is disabled – this is not what you would probably run…

Post: Heikki Tuuri Innodb answers - Part I

… state of Innodb scalability with multiple threads and multiple concurrent transactions ? HT: The scalability in my opinion is ‘mediocre’, and we… remove that serialization. MySQL’s binlog and InnoDB’s log must have the transactions in the same order, for a recovery based… InnoDB’s group commit works again. PZ: You can disable binary logging to get Group Commit back. Though this is often not…

Post: SSD, XFS, LVM, fsync, write cache, barrier and lost transactions

… same result), using innodb_flush_log_at_trx_commit=1 I expect to have all committed transactions even in case of system… see several last N commited transactions. So now time to turn off write-cache on SSD – all transactions are in place now… in conclusion to warranty Durability with SSD we have to disable write-cache which can affect performance results significantly (I have…