I wrote about FlashCache there, and since that I run couple benchmarks, to see what performance benefits we can expect. For initial tries I took sysbench oltp tests ( read-only and read-write) and case when data fully fits into L2 cache. I made binaries for FlashCache for CentOS 5.4, kernel 2.6.18-164.15, you can download it [...]
5.0.83-build17 Percona binaries
July 28, 2009 By 19 Comments
Dear Community, The build 17 of MySQL with Percona patches is available. New features in the release: MySQL-5.0.83 is taken as the basis The new patch innodb_use_sys_malloc.patch is added The new patch innodb_split_buf_pool_mutex.patch is added This patch splits the single global InnoDB buffer pool mutex into several mutexes for different purposes. This reduces mutex contention. [...]
xtrabackup-0.7 (RC)
May 21, 2009 By 4 Comments
We announce next version of our xtrabackup tool and we consider it stable enough to put label RC on it. Changelist includes: – use O_DIRECT by default for handling InnoDB files – use posix fadvise call to disable OS caching of copying files – disable recovery of double buffer Also we added binary builds for [...]
xtrabackup-0.6
April 29, 2009 By 6 Comments
We announce next beta version of our xtrabackup tool. Changelist includes: – set innodb_fast_shutdown=1 on xtrabackup shutdown – set innodb_write_io_threads=10 by default for fast buffer_pool flushing during recovery – build xtrabackup with –with-extra-charsets=complex Bug #357653: innobackupex-1.5.1 –copy-back fails Bug #358194: 2nd-phase is very slow Bug #358266: xtrabackup-0.5 dies with SEGV on bad command line arguments [...]
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 [...]
xtrabackup-0.4, going beta, progress meter
March 30, 2009 By 7 Comments
We added some new features to our backup tool, namely: Now we can handle log file taken during backup with size exceeding 4GB, it may happen if backup takes too long and you have a lot of updates on InnoDB tables Progress meter during recovery step, now you can see what percentage of log file [...]
xtrabackup-0.3, binaries and stream backup
March 13, 2009 By 11 Comments
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 [...]
Updated msl (microslow) patch, installation walk-through!
April 20, 2008 By 17 Comments
For a couple of months there have been no updates to our msl patch, however recently I managed some time to change this. The functionality was extended a little bit and what’s even more important the patch is available for all the recent MySQL releases. To remind anyone who has not yet come across this [...]
TPC-H Run on MySQL 5.1 and 6.0
April 10, 2008 By 16 Comments
We were doing MySQL Performance evaluation on TPC-H queries for the client and they kindly allowed us to publish results which are very interesting. This is obviously not audited TPC-H run, and it can’t be because we used MyISAM tables which are not ACID complaint. Plus we only measured Power to keep things simple. We [...]
