May 25, 2012

Post: Multiple purge threads in Percona Server 5.1.56 and MySQL 5.6.2

and in MySQL 5.6.2 one can have multiple dedicated purge threads. Percona Server 5.1 supports multipletransaction commits and so the purge begins. The tests were performed on Percona’s R900 machine. The scripts and results are on Benchmark Wiki and

Post: SHOW INNODB STATUS walk through

performance counters, statistics, information about transaction processing and all kinds of other things. In MySQL 5 number of Innodb performance counters were exported andand some other system structures. Pending reads and writes are pending requests on buffer pool level. Innodb may merge multiple

Post: MySQL Storage Engines - PBXT

performance effect of it is yet unknown – how transactional system implements logging and dirty buffers flushing has serious impact on performanceread and row write. The file is taking about 8 bytes per row as I understand so it should be very small and

Post: MySQL 4 to MySQL 5 Upgrade performance regressions

… in the processlist for multiple statement transactions. Looking at SHOW INNODB STATUS you would notice large amount of log writes and fsyncs per second… do not read this post as MySQL 5.0 is junk in terms of performance and you should stay on MySQL 4.1 until MySQL has…

Post: How InnoDB handles REDO logging

performs a checkpoint , I thought it might be useful to explain another important mechanism that affects both response time and throughput – The transactionmultiple times since at restart andtransaction will never complete. Both the MySQL configuration and

Post: When would you use SAN with MySQL ?

performance independently from anything else. Performance This…read caching more efficient in its memory while write buffering can too be done by MySQL andMySQL/Innodb specifics ? First, in MySQL if you’re looking for durable transactions the log writemultiple power supplies ECC memory kill-chip and

Post: Analyzing the distribution of InnoDB log file writes

write size. InnoDB writes to the log files in multiples of 512 bytes. Mark Callaghan explained this and some of its performancewrites might accumulate and become much larger. What happens if the log buffer is actually smaller than a transaction

Post: INSERT ON DUPLICATE KEY UPDATE and REPLACE INTO

and what is also important atomically, remember at that time MySQL only had ISAM tables with table locks and no transactionsperform row replacement without reading old data first, and of course because you could set it to replace multiple

Post: Is disk Everything for MySQL Performance ?

perform as good as SSD ? Not really. Leaving all potential serialization issues along you need enough concurrency to utilize multiple hard drives andand another one for Transactional Logs you will often wast 4 hard drives from performance standpoint without a good reason. Having OS and

Post: Heikki Tuuri Innodb answers - Part I

multiple threads and multiple concurrent transactions ? HT: The scalability in my opinion is ‘mediocre’, andperformance boost and it would write at 100MBps vs 33MBps. Any plans to enable tuning of the checkpointing rate? Postgres exposes this data and