xtrabackup 2.0 generates a lot of IO compared to 1.6
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.0 |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.1 |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.2 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
After a migration from XtraBackup 1.6.4 to 2.0.x we noticed that execution time for backups increased by a factor of ~2.5 on all the systems where was deployed (independently from the size from the backups, that could range from tens to hundreds of GB).
===
How to reproduce:
mkdir /data/rene_tmp
cd /data/rene_tmp
wget http://
tar -zxf xtrabackup-
http://
tar -zxf percona-
With 1.6.4:
export PATH=/data/
xtrabackup-
With 2.0.4:
export PATH=/data/
percona-
===
Attached are the output of "vmstat 10" and " iostat -k -d -x 10 /dev/sd[fihg] " , for XtraBackup-1.6.4 and XtraBackup-2.0.4 .
Note: all the instances are EC2 instances with EBS volumes configured on RAID10 . We noticed the same behavior with 4 or 8 EBS volumes, and with chunks of 64kB or 256kB
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 140 lines (+30/-16)2 files modifiedsrc/xbstream.c (+7/-1)
src/xtrabackup.cc (+23/-15)
- Alexey Kopytov (community): Approve
-
Diff: 118 lines (+19/-12)4 files modifiedsrc/ds_tmpfile.c (+4/-1)
src/fil_cur.cc (+1/-1)
src/xbstream.c (+5/-1)
src/xtrabackup.cc (+9/-9)
- Alexey Kopytov (community): Approve
-
Diff: 118 lines (+19/-12)4 files modifiedstorage/innobase/xtrabackup/src/ds_tmpfile.c (+4/-1)
storage/innobase/xtrabackup/src/fil_cur.cc (+1/-1)
storage/innobase/xtrabackup/src/xbstream.c (+5/-1)
storage/innobase/xtrabackup/src/xtrabackup.cc (+9/-9)
This bug could be related to https:/ /bugs.launchpad .net/percona- xtrabackup/ +bug/512163