We had too many requests for deb builds of Percona releases so I could not ignore that and added scripts to build binaries on our Ubuntu 8.10 box. It's going to be only 64bit releases (32bit is dead, isn't it?), and I tested binaries on Debian Lenny system and it seems working fine.

So I prepared binaries for our Build13 (which I actually did not announce to not spam PlanetMySQL a lot, I will figure out another channel for announcements), and you can get it there http://www.percona.com/mysql/5.0.77-b13/deb/, and your feedback is welcome!

As for changes for Build13 it contains InnoDB Data Dictionary restriction patch, which I mentioned before (http://www.mysqlperformanceblog.com/2009/02/11/limiting-innodb-data-dictionary/).

Speaking of deb …

After some sprint coding and testing I am more than happy to declare Xtrabackup getting into alpha stage. And alpha means more that we have some dirty hacks in code / not fully scripted builds / not fully tested all MySQL versions, but backups work just fine! I am able to backup our production box and restore it!

As there were some questions how xtrabackup works, let me explain it: it is supposed to be online, non-blocking backup solution for InnoDB / XtraDB engines for MySQL 5.0 / 5.1 versions. Currently we tested only for 5.0.75 / 5.0.77 and it works just fine. We also modified innobackup script ( thanks InnoDB for making it GPL), so it can be used to backup of MyISAM tables also.

Beside standard --backup and --prepare options we have implemented --throttle to limit IO activity during backup, so we do not hurt production box by intensive file copying operations.

As for now it is available only in source code version on …

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

Here is a list of enhancements:

• Move to MySQL 5.1.31
• Scalability fix — ability to use several rollback segments

Increasing the number of rseg may be helpful for CPU scale of write-intentional workloads. See benchmark results.

The MySQL Proxy was split into

• a chassis which handles cmdline, service, logging, plugin loading
• a core library for the life-cycle, network handling and protocol decoding
• a lua layer wrapping around the internals
• a set of plugins: proxy, admin, debug, replicant

It also contains a few tools that reuse the above libraries:

• mysql-binlog-dump
• mysql-myisam-dump

We dropped libcheck in favour of glib 2.16's g_test_* functions.

Changelog:

Chassis added support for SIGHUP to reopen logfiles added win32-service support added --basedir added experimental --log-backtrace-on-crash added DTrace probes added a angel to keep the chasses alive added --user option to change the system user the proxy runs as added config-file support …

After several important fixes to our patches we made binaries for build12.

Fixes include:

Control of InnoDB insert buffer to address problems Peter mentioned http://www.mysqlperformanceblog.com/2009/01/13/some-little-known-facts-about-innodb-insert-buffer/, also check Bug 41811 to see symptoms of problem with Insert buffer.

http://www.percona.com/docs/wiki/patches:innodb_io_patches

* innodb_flush_neighbor_pages (default 1) - When the dirty page are flushed (written to datafile), this parameter determines whether the neighbor pages in the datafile are also flushed at the same time or not. If you use the storage …

In a nutshell: What’s New in MySQL 5.1.

Release notes: Changes in release 5.1.x (Production).

And yes, very early on (at about two minutes in), I talk about my take on Monty’s controversial post at Oops, we did it again.

To play the video directly, go to http://technocation.org/node/663/play. To download the 146 Mb video to your computer for offline playback, go to http://technocation.org/node/663/download. The slides …

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: …

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. …

I saw Monty's latest rant and I told myself "here we go again." I blogged before about deaf developers, and here's another symptom of the same disease.
This is another case of a developer, a brilliant one, mind you, one of the brightest in the open source arena, but a developer nonetheless, who has a non-user oriented mindset and is inflicting his view on the users.
I will stay clear of the reasons. Why the co-founder of MySQL decides to spoil the party on release day and ambushes his colleagues with a truckload of blame is beyond my understanding.
What concerns me is the patronizing plea that Monty uses against the users. "Don't use MySQL 5.1"? Really? What about the ones who have already been using it for …