June 19, 2013

Comment: How to calculate a good InnoDB log file size

…/entry/innodb_recovery_is_now_faster And from the manual: http://dev.mysql.com/doc/refman/5.5/en/innodb-performance-recovery.html “If you kept the size of your redo log files artificially low because recovery took a long time, you can consider increasing the file size.”

Post: Ultimate MySQL variable and status reference list

MySQL manual,…log_binblogpercona.commanual log_binblogpercona.commanual log_bin_indexblogpercona.commanual log_bin_trust_function_creatorsblogpercona.commanual log_errorblogpercona.commanual log_isamblogpercona.commanual log_outputblogpercona.commanual log…commanual rpl_recovery_rankblogpercona….

Post: How to calculate a good InnoDB log file size

… versions of MySQL. In 5.0 and newer, you can just watch Innodb_os_log_written from SHOW GLOBAL STATUS, too.) mysql> select… up with GB of logs. But also realize this: the recovery time depends not only on the total log file size, but the number… log, fewer log entries will fit into a given log file size, which will generally make recovery faster than you might expect with a big log

Post: Recovery deleted ibdata1

… space – ibdata1 – and redo logs – ib_logfile*. MySQL keeps InnoDB files open all the time. The following recovery technique is based on this…=16 –max-requests=0 –test=oltp –oltp-table-size=1000000 –max-time=3600 –mysql-user=root run sysbench 0.4.12: multi… files ibdata and ib_logfile* do exist Do not restart MySQL until the further recovery strategy is clear

Post: How InnoDB handles REDO logging

… control the transaction log record size, as …log at all, your transaction will never complete. Both the MySQL configuration and hardware will affect the speed at which InnoDB can logrecovery. How does this affect throughput? As the REDO log in InnoDB uses a fixed length circular transaction log

Post: New SpecJAppServer results at MySQL and Sun.

log/mysql/var/ innodb_checksums = 0 innodb_doublewrite = 0 innodb_buffer_pool_size = 5000m innodb_additional_mem_pool_size = 20M innodb_log_file_size = 1600M innodb_log…. innodb_log_file_size = 1600M – another Benchmark optimization. Such large logs typically will cause too long recovery time …

Post: Troubleshooting MySQL Memory Usage

… >> ps.log ps aux | grep mysqld >> ps.log sleep 60 done Check for Table Cache Related Allocations There are cases when MySQL will… + 128560) Recovery system 0 (0 + 0) Threads 425080 (406936 + 18144) Dictionary memory allocated 2623331 Buffer pool size 7864319 Buffer pool size, bytes 128849002496…

Post: Reasons for MySQL Replication Lag

… for replication include setting sync_binlog=1, enabling log_slave_updates, setting innodb_flush_log_at_trx_commit=1. Also note there… good” change as increasing buffer pool size could cause performance problems. MySQL Restart MySQL Restarts may include recovery time but what is the most…

Post: Storing MySQL Binary logs on NFS Volume

… setup. There are good reasons to have binary logs on NFS volume – binary logs is exactly the thing you want to survive the server crash – using them you can do point in time recovery from backup. I was testing high volume replication today using Sysbench: sysbench –test=oltp –oltp-table-size=10000000 –db-driver=mysqlmysql

Post: How would you compress your MySQL Backup

Backing up MySQL Database most people compress them – which can make a good sense in terms of backup and recovery speed as… note the serious leap in compressed file size. Though in this example we used MySQL binary log file which often contains plenty of similar events, which could be the reason for so large size difference…