June 20, 2013

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

… and four 2TB SATA drives in a raid10 for the binlog (yeah I know, not very balanced in terms of I…-indexes=3 –auto-generate-sql –csv=/tmp/mysqlslap_3index_innodb.csv –engine=innodb –auto-generate-sql-add-autoincrement –auto-generate-sql-load…

Post: Maximal write througput in MySQL

… trx_commit=1 : innodb_flush_log_at_trx_commit = 1 and no binary logs trx_commit=0 & binlog : innodb_flush_log_at_trx_commit = 0 and binary logs trx_commit=1 & binlog : innodb_flush_log_at_trx_commit = 1 and binary logs trx_commit=1 & binlog & sync_bin : innodb_flush_log_at…

Post: Beware: ext3 and sync-binlog do not play well together

…-point-selects=0 –oltp-range-size=0 –mysql-table-engine=innodb –mysql-user=root –max-requests=0 –max-time=60 –mysql… – we get 2350 transactions/sec with sync_binlog=1 and 2550 transactions/sec with sync-binlog=0 which is about 10% overhead… be opening binlog with O_DSYNC flag if sync_binlog=1 instead of using fsync will help ? Or may be binlog pre-allocation…

Post: Heikki Tuuri Innodb answers - Part I

… not think so. Sergei Golubchik serialized the MySQL binlog write and the InnoDB log flush with a mutex in 5.1, to…’s binlog and InnoDB‘s log must have the transactions in the same order, for a recovery based on MySQL’s binlog to work. Of course, if you remove that mutex from 5.1, then InnoDB‘s group commit…

Comment: What is innodb_support_xa?

It seems there are many system variables which influence the consistency of the binlog with InnoDB: – sync_binlogbinlog_format – innodb_flush_log_at_trx_commit – innodb_locks_unsafe_for_binloginnodb_support_xa – tx_isolation

Post: INSERT INTO ... SELECT Performance with Innodb tables.

… is not used you can enable innodb_locks_unsafe_for_binlog option, which will relax locks which Innodb sets on statement execution, which… fore replication and point in time recovery, so use innodb_locks_unsafe_for_binlog option with caution. Note disabling binary logs is… enough to trigger relaxed locks. You have to set innodb_locks_unsafe_for_binlog=1 as well. This is done so enabling…

Comment: Benchmarking Galera replication overhead

binlog enabled or disabled? 2) For replication & semisync which settings did you use for sync_binlog, innodb_support_xa? 3) What values of innodb… actually surprised that Galera is slower than regular replication. When binlog & sync_bonlog are enabled, group commit is broken and performance…

Comment: Tuning for heavy writing workloads

Yasufumi, Is it safe to not use binlog in production? I thought binlog is needed for recovery purpose. If binlog is needed, then innodb_support_xa is also needed, right? How much of a performance penalty does enabling binlog & innodb_support_xa incur then?

Post: Missleading Innodb message on recovery

… years ago the feature of Innodb to store copy of master’s position in Slave’s Innodb tablespace got broken. There is…) InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 10000000, file name mysql-bin.005000 InnoDB: Last MySQL binlog file… on this master. What is going on ? The thing is Innodb does not update this information any more however if it…

Comment: Looking at Redis

…? Is it the binlog? innodb_support_xa? What if I have a MySQL server without replication, but still have binlog & innodb_support_xa enabled…