May 24, 2013

Connecting orphaned .ibd files

There are two ways InnoDB can organize tablespaces. First is when all data, indexes and system buffers are stored in a single tablespace. This is typicaly one or several ibdata files. A well known innodb_file_per_table option brings the second one. Tables and system areas are split into different files. Usually system tablespace is located in [...]

Shard-Query EC2 images available

Infobright and InnoDB AMI images are now available There are now demonstration AMI images for Shard-Query. Each image comes pre-loaded with the data used in the previous Shard-Query blog post. The data in the each image is split into 20 “shards”. This blog post will refer to an EC2 instances as a node from here [...]

Performance Schema tables stats

My previous benchmark on Performance Schema was mainly in memory workload and against single tables. Now after adding multi-tables support to sysbench, it is interesting to see what statistic we can get from workload that produces some disk IO. So let’s run sysbench against 100 tables, each 5000000 rows (~1.2G ) and buffer pool 30G. [...]

Percona Server 5.1.56-12.7

Percona Server version 5.1.56-12.7 is now available for download. It is based on MySQL 5.1.56 and is the current stable release in the 5.1 series.

Percona XtraBackup 1.6

Percona XtraBackup 1.6 is now available for download and is the current stable release version of XtraBackup.

Percona Server 5.5.10 (Release Candidate)

Percona Server release 5.5.10-20.1 is now available for download. This is a release candidate for the Percona Server 5.5 series. In addition to MySQL 5.5.10 now being the base version, here are the changes that have been made since Percona Server beta release 5.5.8-20.0:

Percona Server and XtraBackup weekly news, February 26th

Percona Server has a new logo:

Percona Server and XtraBackup weekly news, February 5th

I decided to try a series of blog posts keeping people informed about what’s happening in Percona Server and Percona XtraBackup once a week. I’ll try to digest things, but it turns out to be hard — I want to provide details and links for everything, but then it isn’t really a digest anymore, so [...]

Effect from innodb log block size 4096 bytes

In my post MySQL 5.5.8 and Percona Server: being adaptive I mentioned that I used innodb-log-block-size=4096 in Percona Server to get better throughput, but later Dimitri in his article MySQL Performance: Analyzing Percona’s TPCC-like Workload on MySQL 5.5 sounded doubt that it really makes sense. Here us quote from his article: “Question: what is a [...]

MySQL 5.5.8 – in search of stability

A couple of days ago, Dimitri published a blog post, Analyzing Percona’s TPCC-like Workload on MySQL 5.5, which was  a response to my post, MySQL 5.5.8 and Percona Server: being adaptive. I will refer to Dimitri’s article as article [1]. As always, Dimitri has provided a very detailed and thoughtful article, and I strongly recommend reading if [...]