We are coming with next version of xtrabackup – online backup solution for MySQL 5.0 / 5.1 and InnoDB standard version, plugin modification and XtraDB. We still consider it as alpha version, though it shows perfect stable results in our tests. Let me address two often asked question about xtrabackup: 1) Does it work only [...]
XtraDB benchmarks – 1.5X gain in IO-bound load
December 18, 2008 By 30 Comments
I guess it is first reaction on new storage engine – show me benefits. So there is benchmark I made on one our servers. It is Dell 2950 with 8CPU cores and RAID10 on 6 disks with BBU, and 32GB RAM on board with CentOS 5.2 as OS. This is quite typical server we recommend [...]
MySQL Binaries Percona build10
December 11, 2008 By 12 Comments
We made new binaries for MySQL 5.0.67 build 10 which include next fixes: We addressed concerns about potential logging and statistics overhead, so now you can fully turn on / off query statistics for microslow patch and user statistics in runtime. Next variables were added:
1 2 3 4 5 6 | | slow_query_log | ON | | slow_query_log_file | /var/lib/mysql/slow_query.log | for compatibility with MySQL 5.1 and | userstat_running | OFF | to control gathering of user statistics. |
With both slow_query_log = OFF and userstat_running = OFF [...]
MySQL 5.0, 5.1 and Innodb Plugin CPU Efficiency
December 3, 2008 By 15 Comments
We’ve recently done benchmarks comparing different MySQL versions in terms of their CPU efficiently in TPC-C like Workload. We did it couple of weeks ago so MySQL 5.0.67, MySQL 5.1.29 and Innodb Plugin 1.0.1 were used which are not very recent, though we do not think results will differ a lot with today versions.
What is stored InnoDB buffer pool
September 28, 2008 By 8 Comments
Ever wonder what is stored in InnoDB buffer pool at the moment ? It is not so hard actually – we made a short patch for MySQL 5.0 which show innodb buffer pool content
Percona builds with patches
July 24, 2008 By 16 Comments
As there were many requests for Debian binary packages in our announcement of Percona builds with custom patchsets, we decided to play with it and built .deb, which you can find there: http://www.mysqlperformanceblog.com/mysql/debian/ You can also add the following repositories into your sources.list: deb http://mysqlperformanceblog.com/mysql/debian/5.0/ binary-amd64/ deb http://mysqlperformanceblog.com/mysql/debian/5.0/ source/ deb http://mysqlperformanceblog.com/mysql/debian/5.1/ binary-amd64/ deb http://mysqlperformanceblog.com/mysql/debian/5.1/ source/ [...]
Percona builds with Percona patchsets
July 16, 2008 By 35 Comments
Percona has a strong team of MySQL developers and consultants on board, so we decided to prepare builds with our patches and third-party patches which we think are very useful. We actually use these internally and for our customers. Current releases include: microslow patch (enables microsecond resolution in slow logs) execution plan (show info about [...]
MySQL – to use or not to use
May 28, 2007 By 10 Comments
Reading this slashdot article today and two CIO magazine articles linked from it. Such discussions started at right place at right time always attract a lot of flamers and can be fun to read. What hit me this time is quality of the articles in CIO magazine. If this is what managers suppose to use [...]
InnoDB vs MyISAM vs Falcon benchmarks – part 1
January 8, 2007 By 117 Comments
Several days ago MySQL AB made new storage engine Falcon available for wide auditory. We cannot miss this event and executed several benchmarks to see how Falcon performs in comparison to InnoDB and MyISAM. The second goal of benchmark was a popular myth that MyISAM is faster than InnoDB in reads, as InnoDB is transactional, [...]
InnoDB benchmarks
January 3, 2007 By 15 Comments
There was several changes in InnoDB to fix scalabilty problems, so I ran benchmark to check new results and also compare overall performance of InnoDB in 5.0 and 5.1 before and after fixes. Problems in InnoDB that were fixed: Thread trashing issues with count of theads 100+. In this case performance of InnoDB degraded dramatically. [...]
