Released on June 8, 2011 (Downloads are available here and from the Percona Software Repositories.

Percona Server 5.1.57-12.8 is now the current stable release in the 5.1 series. It is is based on MySQL 5.1.57.

Bug Fixes

• Fixed InnoDB I/O code so that the interrupted system calls are restarted if they are interrupted by a signal. InnoDB I/O code was not fully conforming to the standard on POSIX systems, causing a crash with an assertion failure when receiving a signal on pwrite(). Bug Fixed: LaunchPad: #764395 / MySQL bug #60788 (A. …

MySQL 5.5 and Percona Server 5.5 do not solve all scalability problems even for read only workloads. Workloads which got a lot of attention such as Sysbench and DBT2/TPC-C scale pretty well a they got a lot of attention, there can be other quite typical workloads however which do not scale that well. This is why it is important to test performance and scalability for your application on your hardware if you really want results most relevant for your situation.

In this example I spotted the query pattern responsible for large portion of the load in the application by aggregating query log with mk-query-digest. When I filtered out only queries of this pattern and got a simplified part of production workload which focuses only on one query but yet mimics real world values distribution.

The query looks something like this:

SELECT *  FROM table WHERE deleted = 0 AND group_id IN (62715996, 62716592, 62717660, …

Percona is pleased to welcome Stewart Smith to the team. Stewart does not need an extended introduction for MySQL Community, but just in case: Stewart has a long history with both the MySQL and Drizzle code bases. He’s been one of the core Drizzle developers since the start of the project (working on Drizzle for Sun and then Rackspace), he maintains HailDB and previously worked for MySQL (and then Sun) on MySQL Cluster (NDB).

Stewart joins Percona to lead our development team and will take lead role in both Percona Server and Percona XtraBackup products. You can certainly expect more mutual exchange of features and ideas between Drizzle, …

Part of the InnoDB duties, being an MVCC-implementing storage engine, is to get rid of–purge–the old versions of the records as they become obsolete.  In MySQL 5.1 this is done by the master InnoDB thread.  Since then, InnoDB has been moving towards the parallelized purge: in MySQL 5.5 there is an option to have a single separate dedicated purge thread and in MySQL 5.6.2 one can have multiple dedicated purge threads.

Percona Server 5.1 supports multiple purge threads too, although using more than one is considered experimental at the moment. Unfortunately this patch hasn’t been ported to Percona Server 5.5 yet.

Let’s test these two implementations and find out what benefits, if any, do the additional purge threads bring.

The test workload makes a long history list and then lets purge thread(s) work through it while having a regular OLTP load on the server.  The OLTP part of this is provided by …

We see demand on MacOS binaries and decided to prepare binaries you can download and use. The are marked as “experimental”, as we do not have big history of using MacOS in production, so we are looking for your feedback and bug reports.

Binaries:

• Percona Server 5.5 : http://www.percona.com/downloads/TESTING/Percona-Server-55/Percona-Server-5.5.11-20.2/release-5.5.11-20.2/114/MacOSX/
• Percona Server 5.1: http://www.percona.com/downloads/TESTING/Percona-Server-51/Percona-Server-5.1.56-12.7/release-5.1.56-12.7/226/MacOSX/
• Percona XtraBackup: …

We just pushed to sysbench support for workload against multiple tables ( traditionally it used only single table).

It is available from launchpad source tree lp:sysbench .

This is set of LUA scripts for sysbench 0.5 ( it supports scripting), and it works following way:

- you should use --test=tests/db/oltp.lua to run OLTP test
i.e. prepare

./sysbench --test=tests/db/oltp.lua --oltp-tables-count=25 prepare

run:

./sysbench --test=tests/db/oltp.lua --oltp-tables-count=25 --num-threads=5 run

oltp.lua should understand most options that available for regular sysbench –test=oltp

there are couple other scripts, like
oltp_simple
select
insert
delete
update_index
update_non_index

to support different OLTP …

Percona Server 5.5.11-20.2 is now available for download, including an experimental build for MacOS. Released on April 28, 2011, it is the current stable release in the the 5.5 series.

New Features

1. HandlerSocket, a NoSQL plugin for MySQL, has been updated to the latest stable version as April 11th, 2011.
2. InnoDB fast index creation now works with mysqldump, ALTER TABLE and OPTIMIZE TABLE. (Alexey Kopytov)

Variable Changes

1. Variable innodb_extra_rsegments was removed because the equivalent, ‘innodb_rollback_segments’, has been implemented in MySQL 5.5. (Yasufumi Kinoshita)

Bug Fixes

1. …

Good news for all Percona Software users out there. There are more ways how you can get access to Percona Software. If you’re using Scalr (See also Scalr Project on Google Code) you might be interested in Percona Server roles support Scalr team has announced recently. If you’re Mac user and looking for complete development environment for PHP and MySQL you can check out MNPP which also includes lightweight Ngnix web server instead of Apache.

Now about any Open Source projects including or based on Percona Server or Xtrabackup ? Let us know !

Time for our weekly review of the news! The big news this week is that Percona XtraBackup is ready to try out on Windows. Otherwise, there’s just more steady progress.

One quick note, sort of a “to whom it may concern,” is that the proper trademarked names of our products include “Percona Server”, “Percona XtraDB”, and “Percona XtraBackup”. “XtraDB” and “XtraBackup” are also Percona trademarks, but the proper names of the products include “Percona” at the beginning. The word “xtrabackup” alone and lowercased is only proper when referring to the xtrabackup compiled C binary, e.g. in how-to documentation in a context that includes the whole product name. We are happy to grant written permission for appropriate use of the trademarks. We’re working on publishing an official trademark policy on our website.

• We continue progress towards our Percona Server 5.5 release.
• Percona XtraBackup …

There have been recent discussions about DROP TABLE performance in InnoDB. (You can refer to Peter’s post http://www.mysqlperformanceblog.com/2011/02/03/performance-problem-with-innodb-and-drop-table/ and these bug reports: http://bugs.mysql.com/bug.php?id=51325 and http://bugs.mysql.com/bug.php?id=56332.) It may not sound that serious, but if your workload often uses DROP TABLE and you have a big buffer pool, it may be a significant issue. This can get especially painful, as during this operation InnoDB holds the LOCK_open mutex, which prevents other queries from executing. So, this is a problem for a server with a large amount of memory, like the one we have in our lab: a …