Following Roel’s post, Percona Server on the Raspberry Pi: Your own MySQL Database Server , I thought what other crazy gadget can I run Percona Server on? And having an Asus Nexus 7 Android tablet I decided to give it a try. Anything below contains a risk that you break your tablet if you do [...]
Percona Server on the Nexus 7: Your own MySQL Database Server on an Android Tablet
February 28, 2013 By 11 Comments
Making the impossible: 3 nodes intercontinental replication
January 11, 2012 By 29 Comments
In this post I want to show new possibilities which open with Percona XtraDB Cluster. We will create 3 nodes Cluster with nodes on different continents (Europe, USA, Japan) and each node will accept write queries. Well, you theoretically could create 3 node traditional MySQL ring replication, but this is not what you want to [...]
Make your file system error resilient
August 24, 2011 By 8 Comments
One of the typical problems I see setting up ext2/3/4 file system is sticking to defaults when it comes to behavior on errors. By default these filesystems are configured to Continue when error (such as IO error or meta data inconsistency) is discovered which can continue spreading corruption. This manifests itself in a worst way [...]
Shard-Query EC2 images available
May 11, 2011 By 2 Comments
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 [...]
xtrabackup-0.5, bugfixes, incremental backup introduction
April 7, 2009 By 6 Comments
I am happy to announce next build of our backup tool. This version contains several bugfixes and introduces initial implementation of incremental backup. Incremental backup works in next way. When you do regular backup, at the end of procedure you can see output:
1 2 3 4 5 6 7 8 9 10 | The latest check point (for incremental): '1319:813219999' >> log scanned up to (1319 813701532) Transaction log of lsn (1318 3034677302) to (1319 813701532) was copied. 090404 06:03:29 innobackupex: All tables unlocked 090404 06:03:29 innobackupex: Connection to database server closed innobackupex: Backup created in directory '/mnt/data/tmp' innobackupex: MySQL binlog position: filename 'db02-bin.001271', position 247627478 090404 06:07:58 innobackupex: innobackup completed OK! innobackupex: You must use -i (--ignore-zeros) option for extraction of the tar stream. |
which gives start point 1319:813219999 for further incremental backup. This point [...]
How would you compress your MySQL Backup
June 5, 2008 By 29 Comments
Backing up MySQL Database most people compress them – which can make a good sense in terms of backup and recovery speed as well as space needed or be a serious bottleneck depending on circumstances and approach used. First I should mention this question mainly arises for medium and large size databases – for databases [...]
Innodb Performance Optimization Basics
November 1, 2007 By 75 Comments
Interviewing people for our Job Openings I like to ask them a basic question – if you have a server with 16GB of RAM which will be dedicated for MySQL with large Innodb database using typical Web workload what settings you would adjust and interestingly enough most people fail to come up with anything reasonable. [...]
Site was down today, support and web hosting.
August 31, 2007 By 27 Comments
During last one and a half year we had pretty good track record with MySQL Performance Blog – there were times when site was slow (especially when backup was running) but I do not remember significant downtime, until today we went down for few hours. All this time the site was running on dedicated server [...]
