As we've said before, the Percona team just keeps growing. This time around, I'm pleased to welcome Ryan and Vladimir.

Ryan Lowe initially joined us from Florida (USA) in June. In his previous lives he scaled an Alexa top 1000 site with a sharded MySQL backend, worked in aerospace, worked in telecom, and lots of other things. His background as a consultant, DBA (with Oracle, too!), DBA manager, and programmer makes him a great match for Percona's clients. He also contributed some improvements to Wordpress, and he blogs here and on Pablowe.

Vladimir Fedorkov joins us from Lipetsk in the Russian Federation. (Brrr!) Vladimir and Peter have known each …

Percona has been building and contributing to open-source software since the company was founded, and individually we've been doing the same thing for many years.  We think it's a huge value for our customers and the community.

We're involved in a dozen or so open-source projects, but our three core efforts at the moment are the following:

• Percona patches, which are included in our own MySQL builds and then in OurDelta builds and perhaps others as well
• XtraDB, which is our new high-performance transactional storage engine
• Maatkit, which is a toolkit that provides advanced functionality for MySQL.

We have a team of dedicated MySQL developers working on the server …

Today we announce release 1.0.2-2 of our XtraDB storage engine.

Here is a list of enhancements:

• split-buffer_pool_mutex

The patch splits global InnoDB buffer_pool mutex into several and eliminates waitings on flush IO and mutex when there is no enough free buffers. It helps if you have performance drops when data does not fit in memory.

• innodb_extra_undoslots

InnoDB has a concurrent transaction limit of 1024 because in the standard InnoDB the number of undo slots is fixed value. This patch expands the maximum number of undo slots to 4072 and allows better utilizing modern hardware. (Thank …

As you may know Sun / MySQL made release of community 5.0.75 only as source code release. We made binaries with our patchset.
Patches are mostly equal to build 10
http://www.mysqlperformanceblog.com/2008/12/11/mysql-binaries-percona-build10/, only change:
it includes bugfix for https://bugs.launchpad.net/percona-patches/+bug/308849

You can download binaries (RPMS x86_64) and sources with patches here
http://www.percona.com/mysql/5.0.75-b11/

Entry posted by Vadim | 7 comments

Add to: …

tl;dr: The MySQL community rocks. Percona, XtraDB, Drizzle, SSD storage, InnoDB IO scalability challenges.

For anyone who lives and dies by MySQL and InnoDB, things are finally starting to heat up and get interesting. I’ve been banging the “MySQL/InnoDB scales poorly” drums for years now, and despite having paid Enterprise licenses, I haven’t been able to get anywhere. I was pretty excited when Sun …

Today we officially announce our new storage engine, "Percona XtraDB", which is based on the InnoDB storage engine. It's 100% backwards-compatible with standard InnoDB, so you can use it as a drop-in replacement in your current environment. It is designed to scale better on modern hardware, and includes a variety of other features useful in high performance environments.

Percona XtraDB includes all of InnoDB's ACID-compliant design and advanced MVCC architecture, and adds features, more tunability, more metrics, more scalability on many cores, and better memory usage. We choose features and fixes based on customer requests and on our best judgment of real-world needs. We have not included all the InnoDB patches available. For example Google's well-known InnoDB patch set is omitted (at least for now).

The first version of our new storage engine is 1.0.2-1, which is forked from InnoDB-plugin-1.0.2. …

As Giuseppe just reminded MySQL 4.0 is reaching its end of life in about 2 weeks from now. When it becomes unsupported by MySQL via normal support agreements together with 3.23 version.

At Percona we do not have such restriction and we will continue to support your environment even if you're still on MySQL 4 or 3.23 (we indeed do have customers which are still using 3.23 now)

What does it mean for you in practice ? This means we will continue helping you with issues you're having with MySQL 3.23 or 4.0 and will be happy to backport bug fixes to MySQL 3.23 and 4.0

Supporting MySQL 3.23 and MySQL 4.0 environment is indeed more expensive than current MySQL versions because we can't relay on Sun/MySQL doing any work with bug fixes plus more work is often needed because these versions have lower …

We made new binaries for MySQL 5.0.67 build 10 which include next fixes:

• We addressed concerns about potential logging and statistics overhead, so now you can fully turn on / off query statistics for microslow patch and user statistics in runtime.

Next variables were added:

PLAIN TEXT CODE:

1. | slow_query_log                  | ON                                           |
2. | slow_query_log_file             | /var/lib/mysql/slow_query.log                |
3. for …

Being completely distributed team, meetings are very important for us and this time we went to the Turkey in the end of October (yes, yes I could be faster with sharing photos)

This went we went to Turkey, Antalya region, which is a destination which is very easy to reach from Europe as well as offering great all inclusive deals in the end of the season.

Same as last year we had all spouses/girlfriends and spouses and kids invited to join. I think this was a great tradition of early days MySQL, which Monty and David came up with. Among other things they would finally believe there is a real job real company and real team mates you work with

This year we also missed few guys from the team meeting which had to stay home due to various reason but this is surely majority of the team.

It is fun to compare this picture to one from …

Percona has a new Chief Operating Officer! It is Tom Basil, who was Employee #11 at MySQL and led the Support organization there for almost eight years. He was the founding Director of Support at MySQL, and built it into a team of about 60 people all across the world. Tom was legendary as a manager at MySQL, and we're really looking forward to his experience at Percona.

It sure is funny how things work out. When Peter and Vadim were at MySQL, Tom was their boss for 4 years. Now, Tom works for them! And Tom actively recruited me for a position at MySQL Support almost exactly a year ago, but I joined Percona instead. Perhaps we were meant to work together.

So, why did he resign from Sun/MySQL and come join us? In his own words, slightly paraphrased,

• Vision. Tom knows that we have replicated the vision of MySQL's own founders Monty and David, which was what drew him to work at MySQL in the first place. We're building our …