June 19, 2013

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

…slaves can execute all events and be in sync with the master Change configuration for all servers…, “at the same time” means “at the same binlog position”, so you can perfectly restart the servers…slave #2: # slave #1 mysql> change master to master_auto_position = 1; mysql> start slave; and let’s…

Post: MySQL and Percona Server in LinkBench benchmark

…. Percona Server 5.5 outperforms MySQL in about 2x times. Both MySQL 5.5.30 and MySQL 5.6.11 demonstrate notable drops… we can see small performance drop in MySQL 5.6. In IO-bound cases MySQL still has performance issues around mutexes and… = 8 innodb_write_io_threads = 8 innodb_io_capacity = 5000 sync_binlog=0 max_connections=5000 table_open_cache=5000 table-definition…

Comment: State of the art: Galera - synchronous replication for InnoDB

… IO because of different MySQL configuration. Make sure you’re using the same innodb_* parameters and binlog settings (log-bin, binlog-format, sync-binlog, etc.)

Comment: Is Synchronous Replication right for your app?

… of detail. I have not reviewed or tested semi-sync in official MySQL so I am surprised by this and don’t understand why it occurs. But my peers are interested in semi-sync… 32 clients with semi-sync replication. Apparently each client must wait for it’s turn writing to the binlog and waiting for…

Post: Ultimate MySQL variable and status reference list

MySQLbinlog_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: Beware: ext3 and sync-binlog do not play well together

One of our customers reported strange problem with MySQL having extremely poor performance when sync-binlog=1 is enabled, even though the system… results – we get 2350 transactions/sec with sync_binlog=1 and 2550 transactions/sec with sync-binlog=0 which is about 10% overhead. EXT2… on MySQL side – may be opening binlog with O_DSYNC flag if sync_binlog=1 instead of using fsync will help ? Or may be binlog

Post: Reasons for MySQL Replication Lag

… (and performance in general). Typical problems for replication include setting sync_binlog=1, enabling log_slave_updates, setting innodb_flush_log_at… as increasing buffer pool size could cause performance problems. MySQL Restart MySQL Restarts may include recovery time but what is the most…

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: Jeremy Cole on MySQL Replication

…’re out of sync anyway – whatever sync_binlog option was set to. Well it is still a bit better with sync_binlog enabled as slave…. I guess Jeremy speaks about enabling binary log and setting sync_binlog option which is good for safe replication. But it is… sync_binlog changes things. Two logs are synced now which requires seeks which make certain disks to flush their cache. Watch out for MySQL

Post: Maximal write througput in MySQL

… what maximal amount transactions per second we can get using MySQL and XtraDB / InnoDB storage engine if we have high-end… 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…