On Friday I gave a presentation on “MySQL Query Patterns, Optimized” for Percona MySQL Webinars. If you missed it, you can still register… an infinite variety of queries. The query optimizer analyzes queries for common patterns the MySQL designers know can be improved. But there’s a finite amount of engineer-years spent developing and testing the query optimizer…
Post: The small improvements of MySQL 5.6: Duplicate Index Detection
May 31, 2013 By Leave a Comment
… on the query optimizer and the MySQL version, we always recommend to check manually the optimizations proposed by Percona Toolkit. The MySQL server, of course, cannot risk to block directly all cases. A set of MySQL utilities…
Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency
May 22, 2013 By Leave a Comment
… Benchmark. In my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default settings using…. A star schema presents some unique challenge to the database optimizer. The SSB benchmark consists of four sets of queries. Each… [mysqld] datadir=/mnt/mysql56/data basedir=/usr/local/mysql socket=/var/lib/mysql/mysql.sock user=justin innodb_buffer_pool_size=64G innodb…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
June 7, 2013 By Leave a Comment
… nothing wrong with a virtual-machine approach, but for the optimal production deployment you want two identical physical boxes with at…: Incorrect information in file: ‘./mysql/servers.frm’ ERROR: 1033 Incorrect information in file: ‘./mysql/servers.frm’ Running mysql_install_db under strace, I…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
…-30.2 milestone at Launchpad. New Features: Percona Server for MySQL has implemented priority connection scheduling for the Thread Pool. (Alexey… secondary keys from deferred key creation optimization. Bug fixed #1081016 (Alexey Kopytov). Percona Server for MySQL was built with YaSSL which could… fixed #1015506 (Alexey Bychko). Percona Server for MySQL was missing help texts in the MySQL client because the help tables were missing…
Post: MySQL alternative Percona Server 5.1.68 -14.6 now available
April 19, 2013 By 3 Comments
… fixed #1031427 and #1051874. When mysqldump was used with –innodb-optimize-keys option it produced invalid SQL for cases when there… secondary keys from deferred key creation optimization. Bug fixed #1081016. When mysqldump was used with –innodb-optimize-keys and –no-data options… fixed #1032139. Percona Server was missing help texts in the MySQL client because the help tables were missing. Bug fixed #1041981…
Post: What I'm looking forward to at Percona Live (MySQL Users Conference)
April 4, 2013 By 1 Comment
… 10th year attending and speaking at the MySQL Users Conference (as the Percona Live MySQL Conference and Expo was originally called back… Innodb and Performance Optimization Tutorial as well as talk about Goal-Driven Performance Optimization and Choosing storage systems for MySQL Do Business. This…
Post: 5 Percona Toolkit Tools for MySQL That Could Save Your Day: April 3 Webinar
March 22, 2013 By Leave a Comment
… presentation you’ll learn how to perform typical but challenging MySQL database administration tasks. My focus will be on the following… on “5 Percona Toolkit Tools for MySQL That Could Save Your Day”Percona Toolkit for MySQL is a must-have set of… solve typical, real-world MySQL database administration challenges, such as: Selecting which queries you should try to optimize to get better response…
Post: Keynotes, BOFs, and the Community Networking Reception at Percona Live MySQL Conference and Expo
April 15, 2013 By 1 Comment
…sessions including presentations on Oracle MySQL, Percona Server, and MariaDB during the Percona Live MySQL Conference. Percona Live MySQL Conference Keynotes Tuesday …10.0 & What’s New With the Project” Sergei Petrunia, Optimizer Developer, and Colin Charles, Chief Evangelist, MariaDB, for Monty …
Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2
April 12, 2013 By 3 Comments
… a great optimization in itself, applies only to the following kinds of transactions: MySQL transactions started with START TRANSACTION READ ONLY MySQL transactions created by a non-locking SELECT statement in the autocommit mode. The relevant optimization in MySQL 5.6… the perfect case for read-only optimization in MySQL 5.6 and as you can see MySQL 5.6 shines in this benchmark…
