I recently had the chance to talk to the San Francisco MySQL Users Group and any group that gets 80 plus regulars to attend meetings is impressive. That night they had 280 people RSVP! And a better than average percentage appears. Thanks to Theo, Mike and Erin — the organizers for the invite. I also had the chance to ask Erin O’Neill the secrets of how they run their meetings.
The MySQL optimizer makes the decision of what execution plan to use based on the information provided by the storage engines. That information is not accurate in some engines like InnoDB and they are based in statistics calculations therefore sometimes some tune is needed. In InnoDB these statistics are calculated automatically, check the following blog post for more information:
I’ve never been a very big fan of MyISAM; I would argue that in most situations, any possible advantages to using MyISAM are far outweighed by the potential disadvantages and the strengths of InnoDB. However, up until MySQL 5.6, MyISAM was the only storage engine with support for full-text search (FTS). And I’ve encountered many customers for whom the prudent move would be a migration to InnoDB, but due to their use of MyISAM FTS, the idea of a complete or partial migration was, for one reason or another, an impractical solution.
Don’t forget to Register for the March 12 Virtual Developers Day. Two training tracks — one for beginners and the second is a MySQL 5.6 deep dive. The event will repeat on March 19th for Europe, Middle East, Africa, and some Asian Countries.
Percona is glad to announce the release of Percona Server for MySQL version 5.5.29-30.0 on February 26th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.29, including all the bug fixes in it, Percona Server 5.5.29-30.0 is now the current stable release in the 5.5 series.
In many Benchmarks we can see performance compared with rather high level of concurrency. In some cases reaching 4000 or more concurrent threads which hammer database as quickly as possible resulting in hundreds or even thousands concurrently active queries.