May 24, 2012

Post: How to estimate time it takes Innodb to Recover ?

in Innodb talks and during consulting engagements. It is well known to get better performance you should normally set innodb_logto the disk and undo phase – rolling back uncommitted transactions. As MySQL 5.0 these seems to be done in the background. In the future to

Post: How InnoDB handles REDO logging

… be seen by enabling the innodb_recovery_stats option in Percona Server, which allows you to see the progress made during recovery. How does this affect throughput? As the REDO log in InnoDB uses a fixed length circular transaction log, the…

Post: Heikki Tuuri Innodb answers - Part I

Innodb operations while I see it causing problems every so often. Q16: How Innodb decided how many pages toto enable tuning of the checkpointing rate? Postgres exposes this data and allows the user toInnoDB‘s log must have the transactions in the same order, for a recovery based on MySQL’s binlog to

Post: How to recover a single InnoDB table from a Full Backup

to another. The reason is that the table definition is stored in the InnoDB shared tablespace (ibdata) and the transaction IDs and logto work. You can read more about this feature in Percona Server Documentation In the next blog post I’ll explain how to

Post: MySQL Users Conference - Innodb

to lock all rows in Innodb right now) I however did not get exact plans on this one. In general I should mention InnodbInnodb to unleash performance such as multiple purge threads or parallel log recovery features, which he however needs to test properly before really enabling it. Innodb

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

… have to set innodb_locks_unsafe_for_binlog=1 as well. This is done so enabling binary log does not cause unexpected changes in locking… locks to cause the problems. To complete this article I should show how wait caused by this statement will look in SHOW INNODB STATUS: —TRANSACTION 0…

Post: SSD, XFS, LVM, fsync, write cache, barrier and lost transactions

innodb_flush_method, with the same result), using innodb_flush_log_at_trx_commit=1 I expect to have all committed transactions even inenable write-cache you may lose transactions. So in final conclusion: 1. Intel SSD X25E is NOT reliable in default mode 2. To

Post: MySQL 4 to MySQL 5 Upgrade performance regressions

… it mentioned in MySQL 4.1 to 5.0 upgrade notes ? ? Furthermore if there were no good ideas how to make XA to work with… have to have innodb_flush_logs_at_trx_commit=1 so transactions are truly durable. You have to have log-bin enabled to get replication or point in time… “commit” queries in the processlist for multiple statement transactions. Looking at SHOW INNODB STATUS you would notice large amount of log writes and fsyncs…

Post: MySQL Limitations Part 2: The Binary Log

InnoDB transaction log would work fine if a) all the data were in InnoDB, and b) InnoDB‘s data didn’t have tohow hard it is. It’s worth noting that PBXT does replication through its transaction logs

Post: MySQL 5.5.8 - in search of stability

Transactions per 10 seconds. dirty page – This graph will contain the percentage of dirty pages in the InnoDBin innodb_log_file corresponds to changed pages in the buffer pool. You can compute this value as Log