MySQL Performance Blog

Microslow patch is used by many DBAs and developers to accurately time their queries and to catch those which run less than a second as they can also be a performance killer for a busy application.

Recently I have started the development of an updated version of the patch. The basic idea is the same as for its predecessor - to get more information about query execution logged into slow log, however the new version is loaded with a set of cool new features.
[read more...]

Looking at the Feedback I got for other Presentations Proposals I thought I indeed should submit general presentation focusing on Web Application performance tuning and explaining how you analyze performance and why do you do it this way, so here it is:

Performance Analysis of MySQL powered Web Applications
In this session we’ll go beyond MySQL Performance Optimization and look at full stack performance tuning for Web Applications. It is practical session about Performance Tuning Methodology.
[read more...]

Suppose you want to remove auto_increment from 100G table. No matter if it’s InnoDB or MyISAM, you’d usually ALTER TABLE `huge_table` CHANGE `id` `id` int(6) NOT NULL and then wait hours for table rebuild to complete. If you’re unlucky i.e. you have a lot of indexes and not too much RAM - you could end up waiting days. If you want to make this happen quick - there’s another way. Not documented, but works well with both - InnoDB and MyISAM.
[read more...]

Its almost a month since I promised Heikki Tuuri to answer Innodb Questions. Heikki is a busy man so I got answers to only some of the questions but as people still poking me about this I decided to publish the answers I have so far. Plus we may get some interesting follow up questions out of this.

I had added my comments to some of the questions. HT will stand for Heikki Tuuri in the answers and PZ for myself.
[read more...]

What is the difference between “MySQL Support” and “Support for MySQL” ?
In my mind there is not much difference in meaning just first one is shorter and I would use it also because how people would search stuff in Google.

It turns out however there is significant legal differences - first one would be MySQL Trademark violation but not the second one.
I learned it because MySQL contacted me about our consulting company new “corporate” site and rename Services appropriately.
[read more...]

Try number two. We have moved to the new server yet again, now it is server hosted by ServerBeach as recommended by Kevin Burton and few other guys.

Lets hope this will run stable and we’ll not need to move it back in emergency in less than a week as we had to last time.

Up to this point it all was running pretty well, with only minor issues. We got CentOS 5 on the box as we wanted, however we could not request custom partitioning - I really prefer to keep all important data on LVM volume so it is easy to backup.

OK, I am not getting too much people feedback on what would they like to hear about on MySQL Users Conference, so I went ahead and submitted few presentation ideas.

I do not expect all of them would be accepted, furthermore it would be hard to prepare so many good presentations if they are so please let me know if anything of this is of special interest for you. When I would be able to show that to organizers to help with decision.

Also let me know if you have submitted similar talk as in this case there may be way to work together to produce better talk instead.
[read more...]

About three months ago I announced ClickAider to become available to general public. And I think it is about the time to write about the progress we have with this project for those who interested.

The project generates decent interest and we have about 3000 sites Registered over this time, which I consider decent number especially as we did not do much of advertisement and PR keeping it low profile and working out few bugs which we might have.
[read more...]

If you have been MySQL User for many years you might remember the times when MySQL had “zero bugs policy”, this is when all known bugs really were fixed before release was made. To be honest at that time bugs were reported via bugs mailing list not via bugs database as they are now so they were not tracked so accurately but still there was intention and all known serious bugs were fixed before release was made.

Over years this policy had few changes, transforming to something like “no critical bugs in production releases” and in practice releases moved to predictive schedule rather than based on the moment when all bugs were fixed.
[read more...]

It is submission time now, with about one week left till proposal submission deadline. Both me and Vadim had submitted few talks to the Grand Jury which will make elite selection of sessions for MySQL Users Conference and we plan to submit few more.

Our experience in MySQL is rather broad - we can prepare talks in areas of MySQL Performance Optimization, Scaling, High Availability and Replication , efficient application design, good operations practices or take one of applications we helped with and show its internals as a case. We can do some new talks or update some of old talks with modern material such as those about general MySQL Performance Optimization or Innodb Tuning.

Anyway we would like to hear what would you like to hear about on MySQL Users Conference and if that falls in our area of experience we’ll propose such talk !