…. So assuming you have innodb_flush_log_at_trx_commit=1 and sync_binlog=1 you will have 4 “sync” operations in… in Innodb log to commit it and finally there is record in Binary log to commit transaction followed by commit transaction in Innodb… a lot of synchronous writes which are fully serialized because group commit in Innodb was broken in 5.0 and it is…
Comment: Storing MySQL Binary logs on NFS Volume
… or remote storage as the place where binlog archiving is done rather than where the binlogs are written in the first place… I know the Facebook patch also does. I assume that binlog sync to local storage accelerated by HW RAID write cache is much faster than binlog sync to NFS. Given the lack of group commit in InnoDB that can make a…
Comment: How many fsync / sec FusionIO can handle
prepare_commit_mutex guarantees there is no group commit as soon as the binlog is enabled. What fraction of InnoDB deployments that care about performance run with the binlog off?
Post: Announcing Percona Server 5.5.27-29.0
… data scans. Number of binlog files can be restricted when using Percona Server with the new max_binlog_files option. Bugs Fixed… Ormond Lorch III). Option expire_logs_days was broken by group_commit patch introduced in Percona Server 5.5.18-23.0… bool options. Bug fixed #881001 (George Ormond Lorch III). The binlog shouldn’t be rotated while it contains XA transactions in…
Comment: How Does Semisynchronous MySQL Replication Work?
… Enhanced Semi-Sync but suspect that the implementation will make commit stalls even worse as it probably increases the duration of… time for which prepare_commit_mutex is held. This needs to be integrated with the changes for group commit so that we can… the PREPARED transactions into the binlog 3) wait for one slave to ACK all of them 4) commit on the master The…
Comment: FlashCache: tpcc workload with FusionIO card as cache
… on FusionIO as well? Do you use binlog? Group commit is reportedly to be still broken when binlog is enabled (http://kristiannielsen.livejournal.com… it’s possible to get sustained 10K+ trans/sec if binlog is enabled.
Post: MySQL 5.6: Improvements in the Nutshell
…Cache – Improved Adaptive Flushing – Page Cleaner/Separate Flush Thread – Group Commit for Binary Log – Fight Cache Coherence and False Sharing…Multi-Threaded Slave – Global Transaction Identifiers – Crash Safe Slave and Binlog – Replication Event Checksums – Time Delayed Replication – Server UUID – …
Comment: 7 Reasons why MySQL Quality will never be the same
… the master was likely to make the binlog and InnoDB out of sync. The sync_binlog option was added in 4.1… solved by the use of internal XA which unfortunately broke group commit (but I am willing to give that up for safety…
Comment: Percona Server 5.5.15 + Galera 21.1-beta2
… to one master. (And if accounting for the group-commit bug with sync_binlog=1 there’s of course a huge performance boost…
Comment: Testing the Group Commit Fix
This is a very important fix. MySQL Server 5.5 has a fix for the InnoDB Group Commit (innodb_support_xa=1). But sync_binlog=1 is still a performance killer – also with a battery-backed cache controller. Some graphics “MySQL Server 5.5 versus Percona Server 5.5″ for these cases are interesing.

