June 20, 2013

Post: MySQL and Percona Server in LinkBench benchmark

innodb_buffer_pool_size = 30G innodb_flush_method = O_DIRECT innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size=128M innodb

Post: Recovery beyond data restore

… have to be very careful such as using sync-binlog innodb_flush_logs_at_trx_commit=1 and only using Innodb tables to be OK in most cases. There… DRBD to get a standby MySQL server or at least synchronously replicated master binary logs. If you can’t loose any single… or disk failure. Though it also can be things like Innodb corruption or soft crash which you can’t recover promptly…

Post: Maximal write througput in MySQL

…binary logs 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_trx_commit = 1…

Post: Testing the Group Commit Fix

… recover-ability requirements, that is innodb_flush_log_at_trx_commit=1, sync_binlog=1 and you do not have storage that provides fast syncs (i.e. you do… (write-back cache is disabled), innodb_flush_log_at_trx_commit=1 and sync_binlog=1 or in tabular format: Threads Nofix Group Commit fix 1 21.51 21…

Post: Comparing Percona XtraDB Cluster with Semi-Sync replication Cross-WAN

… Percona XtraDB Cluster server 5.5.24.  Innodb durability was disabled for all tests (innodb_flush_log_at_trx_commit=2).  All other settings were the same… 32 clients with semi-sync replication.  Apparently each client must wait for it’s turn writing to the binlog and waiting for…

Post: New SpecJAppServer results at MySQL and Sun.

innodb_log_file_size = 1600M innodb_log_buffer_size = 16M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 300 innodb_thread_concurrency = 0 innodb_sync_spin_loops = 40 innodb_locks_unsafe_for_binlog = 1 innodb_max…

Post: Storing MySQL Binary logs on NFS Volume

… was reachable even with binary log stored on NFS volume. This number is for sync_binlog=0 and innodb_flush_log_at_trx_commit=2 I noted however if… something which requires a network roundtrip when the binary log is written at the same time as slave-feeding thread is reading…

Post: Ultimate MySQL variable and status reference list

innodb_flush_log_at_trx_commitblogpercona.commanual innodb_flush_methodblogpercona.commanual innodb_force_recoveryblogpercona.commanual Innodb_have_atomic_builtinsblogpercona.commanual innodb_io_capacityblogpercona.commanual innodb_lock_wait_timeoutblogpercona.commanual innodb

Comment: Product to try: MySQL/MariaDB-Galera 0.8

…Henrik I agree that question on innodb_flush_log_at_trx_commit=1 and sync_binlog=1 ( and Galera also recommends innodb_doublewrite=0 in cluster setup) is rather… cover different combination. My couple cents: you may use innodb_flush_log_at_trx_commit=2/sync_binlog=0 in single node setup, but you still may want…

Comment: New Forum Categories: Help Wanted, For Hire

innodb_flush_log_at_trx_commit=1 innodb_flush_method=O_DIRECT innodb_thread_concurrency=16 innodb_buffer_pool_size = 4500M innodb_lock_wait_timeout=60 innodb_log_buffer_size = 32M innodb_log