Useful results for when we move to SSDs.. Were sync_binlog=1 and innodb_flush_at_trx_commit=1 ?
Post: Ultimate MySQL variable and status reference list
…binlog_cache_sizeblogpercona.commanual Binlog_cache_useblogpercona.commanual binlog_direct_non_transactional_updatesblogpercona.commanual binlog_do_dbblogpercona.commanual binlog_formatblogpercona.commanual binlog_ignore_dbblogpercona.commanual binlog…
Post: Testing the Group Commit Fix
…_log_at_trx_commit=1, sync_binlog=1 and you do not have storage that provides fast syncs (i.e. you do not… is disabled), innodb_flush_log_at_trx_commit=1 and sync_binlog=1 or in tabular format: Threads Nofix Group Commit fix…-concurrent workload. The last test was done with a disabled sync_binlog=0 and without write-back cache: Threads Nofix Group Commit…
Post: Maximal write througput in MySQL
… used ROW based replication for 5.1) – do we have sync_binlog options. So why would not take these as variable parameters… logs trx_commit=1 & binlog & sync_bin : innodb_flush_log_at_trx_commit = 1 and binary logs and sync_binlog=1 There are results…. So with binary logs serialization is getting even worse. Enabling sync_binlog makes things really bad, and maximal results I have is…
Comment: Maximal write througput in MySQL
… EXT3 performs surprisingly bad with sync_binlog=1 http://www.mysqlperformanceblog.com/2009/01/21/beware-ext3-and-sync-binlog-do-not-play-well-together/ In any case it looks like sync_binlog has very bad overhead… fsync per commit in single client (because of XA) with binlog it should be 3 as I understand – the fact performance…
Post: No more MySQL Crash Safe Replication in 5.0 ?
… done: InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 115, file name portland-bin.001717… has much higher performance overhead – you can run slave with –sync-binlog and –log-slave-updates so you can see what last… prints position in the MySQL binary log: InnoDB: Last MySQL binlog file position 0 589600615, file name ./galax-bin.001376 This…
Post: MySQL Crash Recovery
… log corruption – Binary log may become corrupted and out of sync with database content. This will sometimes break replication but if…. sync_binlog Is helping by syncing binary log, but at performance penalty. If using Innodb you also might with to use innodb-safe-binlog… appropriate position even if master.info file is out of sync but I would not be basing my failure handling scenarios…

