Percona, and Yasufumi Kinoshita who works for Percona, received two awards from the O’Reilly MySQL Conference co-chairs on behalf of the committee that voted on the nominees. The awards were: to Yasufumi as O’Reilly MySQL Community Contributor of the Year 2011 for InnoDB performance improvements, and to XtraBackup as O’Reilly MySQL Application of the Year [...]
Flexviews – part 3 – improving query performance using materialized views
April 4, 2011 By 20 Comments
Combating “data drift” In my first post in this series, I described materialized views (MVs). An MV is essentially a cached result set at one point in time. The contents of the MV will become incorrect (out of sync) when the underlying data changes. This loss of synchronization is sometimes called drift. This is conceptually [...]
Spreading .ibd files across multiple disks; the optimization that isn’t
December 25, 2010 By 23 Comments
Inspired by Baron’s earlier post, here is one I hear quite frequently – “If you enable innodb_file_per_table, each table is it’s own .ibd file. You can then relocate the heavy hit tables to a different location and create symlinks to the original location.” There are a few things wrong with this advice:
An argument for not using mysqldump
November 8, 2010 By 26 Comments
I have a 5G mysqldump which takes 30 minutes to restore from backup. That means that when the database reaches 50G, it should take 30×10=5 hours to restore. Right? Wrong.
Percona at WebConf Riga 2010
October 6, 2010 By Leave a Comment
My colleague Aleksandr Kuzminsky will be speaking at WebConf Riga 2010 next month on XtraBackup: Hot Backups and More and Recovery of Lost or Corrupted InnoDB Tables. WebConf is the first big conference of its kind in the Baltic states (Estonia, Latvia, Lithuania) and we are very happy to be participating. In addition to Aleksandr’s [...]
Why you can’t rely on a replica for disaster recovery
July 31, 2010 By 25 Comments
A couple of weeks ago one of my colleagues and I worked on a data corruption case that reminded me that sometimes people make unsafe assumptions without knowing it. This one involved SAN snapshotting that was unsafe. In a nutshell, the client used SAN block-level replication to maintain a standby/failover MySQL system, and there was [...]
The Doom of Multiple Storage Engines
May 8, 2010 By 22 Comments
One of the big “Selling Points” of MySQL is support for Multiple Storage engines, and from the glance view it is indeed great to provide users with same top level SQL interface allowing them to store their data many different way. As nice as it sounds the in theory this benefit comes at very significant [...]
MongoDB Approach to Availability
April 30, 2010 By 2 Comments
Another thing I find interesting about MongoDB is its approach to Durability, Data Consistency and Availability. It is very relaxed and will not work for some applications but for others it can be usable in current form. Let me explain some concepts and compare it to technologies in MySQL space. First I think MongoDB is [...]
Presentations Announcement: 2010 O’Reilly MySQL Conference & Expo
April 29, 2010 By 4 Comments
The Percona team participated at this year’s O’Reilly MySQL Conference & Expo held April 12-15, 2010 in Santa Clara, California. We gave a lot of talks on…
Author: Peter Zaitsev, Justin Swanhart
MySQL Graphing and Trending with Cacti
Author: Baron Schwartz
Percona‘s Performance and Feature Enhancements to MySQL and InnoDB
Author: Bill Schuler, Baron Schwartz…a Bottleneck
Author: Morgan Tocker
XtraBackup Hot Backups and More
Author: Vadim Tkachenko, Morgan Tocker
You can also read more about this conference on Percona site.
How fast is FLUSH TABLES WITH READ LOCK?
April 24, 2010 By 30 Comments
A week or so ago at the MySQL conference, I visited one of the backup vendors in the Expo Hall. I started to chat with them about their MySQL backup product. One of the representatives told me that their backup product uses FLUSH TABLES WITH READ LOCK, which he admitted takes a global lock on [...]
