The MySQL database has become the world’s most popular open source database because of its fast performance, high reliability and ease of use. The DBAs expect the same virtues from a backup solution for MySQL. Often times we are asked what performance to expect from Zmanda Recovery Manager (ZRM) for MySQL. That is why recently we measured backup and recovery performance for MyISAM and InnoDB storage engines using various backup methods available with ZRM.
In our testing we used MySQL 5.0 running Netflix databases available as part of Netflix Prize project. Our 2-way Red Hat Enterprise 4 server with 4 GB of memory was able to copy large files with an average transfer rate of 37 Mb/s.
All details and results are described in a white paper available with a free registration to the Zmanda Network. Here are the important takeaways:
- Logical backups and especially recoveries are slo-o-o-o-w. For MyISAM storage engine the transfer rate for backup was 5 MB/s and only 2 MB/s for recovery. Backup of InnoDB was only slightly faster.
- Raw backups and recoveries are much faster than logical ones. For example, for MyISAM the transfer rate was 25 MB/s for raw backup and 40 MB/s for recovery.
- In our testing we did not find any significant difference in backup and recovery transfer rates for different sizes of the database.
- The READLOCK time is the shortest with raw backups done via LVM snapshots managed by ZRM. The shorter the READLOCK time the better for an application and users.
That testing was our first step in measuring the performance of ZRM for MySQL when there was no user activity. We do understand that DBAs are concerned with backup performance when MySQL is used. That is why we will continue to measure ZRM performance including conditions with heavy user activity.