Get flash to fully experience Pearltrees
MySQL Performance: Using Performance Schema Two weeks ago I was very lucky to meet in Paris Marc Allf (one of developers of MySQL Performance Schema) and get all details about Performance Schema directly from the source :-) I would say I'm very excited about this feature giving so enormous potential to observe any activity inside of MySQL, as well by a great flexibility of the proposed solution! :-) However, discussing with Marc and going over a day more and more in depth, I've got some remarks that I needed to group, summarize and then express (and vacation time helping here a lot ;-)) My points will not be about adding some new extensions, but rather fixing some core issues which I consider important (and, please, correct me if you're not agree, express your ideas, etc - it's one of the cases where a quantity of opinions will be easily transformed into the quality solution for sure :-))
Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Last edited 08/28/2008 MySQLTuner is a Perl script that analyzes your MySQL performance and, based on the statistics it gathers, gives recommendations which variables you should adjust in order to increase performance. That way, you can tune your my.cnf file to tease out the last bit of performance from your MySQL server and make it work more efficiently. This document comes without warranty of any kind!
In order to automate the optimization of SQL queries in Ruby on Rails, I wrote this script to parse the output of the logs. It finds all the unique SQL queries made by different controllers, and runs an SQL EXPLAIN for each. This is really good for finding missing indexes and large table scans. I have only tested this on Mac/MySQL, so your mileage may vary (it uses *NIX file paths). This script has saved me MUCH time. Of course, when optimizing queries, don't go overboard on eager loading.
There are a couple of options available to get consistent backups from MySQL. Use mysqldump with FLUSH TABLES WITH READ LOCK Use a slave with STOP SLAVE and your favourite backup tool. For innodb, use the commerical backup tool ibbackup Use LVM (Logical Volume Manager) snapshots with FLUSH TABLES WITH READ LOCK Shutdown the database.