May 25, 2012

Comment: Benchmarking single-row insert performance on Amazon EC2

…, I am not testing IO performance and instead trying to optimize writes, also the durability requirements are not that stringent and… second worth of data, hence I did not test with innodb_flush_log_at_trx_commit=1. I would also not recommend running on EBS with innodb_flush_log_at_trx_commit=1, because IO times on…

Post: Load management Techniques for MySQL

One of the very frequent cases with performance problems with MySQL is what they happen every so often or certain times. Investigating them we find out what the cause is some batch jobs, reports and other non response time critical activities are overloading the system causing user experience to …

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

… the join optimizations when the workload fits entirely in memory. For the purpose of benchmarking in-memory workload, the InnoDB buffer pool… are the join optimizations when the workload is IO bound. For the purpose of benchmarking IO bound workload, the InnoDB buffer pool… 2.2G Innodb_data_reads 329115 355323 143808 335526 16164 15506 Innodb_pages_read 329115 355323 143808 358308 144798 144881 Innodb_rows_read…

Post: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

….5 FLUSH TABLES WITH READ LOCK does not work as optimally as you could think it works. Even though with general… gridlock one way or another. If you’re just using Innodb tables and you’re not actively changing users, stored procedures…

Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

… were made in the MySQL config: optimizer_switch=’index_condition_pushdown=off’ optimizer_switch=’mrr=on’ optimizer_switch=’mrr_sort_keys=on’ (only… 20920 23734 Innodb_buffer_pool_read_requests 1361851 1264739 1235472 1263290 1235781 Innodb_buffer_pool_reads 120548 102948 76882 102672 76832 Innodb_data….89G 1.53G Innodb_data_reads 120552 123872 100551 103011 77213 Innodb_pages_read 120548 123868 100551 123592 100566 Innodb_rows_read 799239…

Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact

… working with Peter in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one. So in the same way this blog post is aimed at a new optimizer enhancement Index Condition Pushdown (ICP). Its available in both MySQL…

Post: MariaDB 5.3 is released as GA!

… very good indeed. Peter will present the results in an “optimizer standoff” talk at the upcoming MySQL conference, and Timour and… offers microsecond timestamp support, as well as a lot of optimizer improvements. Even the standard MySQL 5.5 offers pluggable authentication…, better diagnostics, improvements to partitioning, and the addition of multiple InnoDB buffer pools. Best of all, MariaDB 5.5 might be…

Comment: Should you move from MyISAM to Innodb ?

… my tables to innodb and currently going into queries and db optimization. Could someone really confirm where should i use Innodb. Big table ie. users? comments? etc… i just compared MyIsam to Innodb… gain from MyIsam. Will this be better once i tuned InnoDb settings? and add query cache? Thanks a lot for all…

Comment: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

… variation in InnoDB statistics. It is not much the Optimizer can do about that. In MySQL 5.6 you can use InnoDB Persistent… and plan stability. (See http://oysteing.blogspot.com/2011/05/innodb-persistent-statistics-save-day.html). You can also reduce the…

Comment: Instrumentation and the cost of Foreign Keys

… because the optimizer has more information about what needs to be done and the plan is created faster. Does innodb get any…