MySQL Performance Blog

Our company, Percona is even more Virtual than MySQL AB - we have no offices and 100% of staff members work out of their homes (or traveling, onsite with customers etc). We also probably have just couple of cities where more than one Employee lives.

I have now posted slides for the talk I gave in Zurich last week in MySQL Performance Presentations section.

That was fun talk and fun trip in general. Thank you for inviting.

I’m visiting customer in Zurich next week and also was invited to give a talk on MySQL Performance Wednesday November 21.
If you’re in the area please feel free to drop by I’ll start by talking about Query Optimization and we’ll keep it interactive to see what else audience would like to know.

Entry posted by peter | No comment

People are sometimes contacting me and asking about bugs like this which provide a trivial way to crash MySQL to the user with basic privileges and asking me what to do.

My answer to them is - there is nothing new to it and they just sit should back and relax

Baron have been updating you a lot about chapter by chapter progress so I should not repeat it, instead I thought it would be a good idea to write a bit about how we work on the book.

Generally, quite similar to the previous book this is long process, which is probably what happens when busy people attempt to get time to write a book. I started working on book Outline with Andy Oram (our great editor) about a year ago.

I now got answers to the second portions of the questions you asked Heikki. If you have not seen the first part it can be found here.

Same as during last time I will provide my comments for some of the answers under PZ and will use HT for original Heikkis answer.

Look at this post recently published on TechCrunch - It is ugly standard 404 error message, but what is interesting is the server line which shows nginx 0.5.32

I have checked and indeed images served from assets.hulu.com have nginx server in response header.

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.

CONNECTION IDENTIFIER

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.

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.

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.

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.