Yes, it seems the reason is that stream uses tar4ibd in new version
Unfortunately there is not so much we can do, as tar4ibd is recommended for stream, and it is needed to guarantee no data corruption.
time ./innobackupex-1.5.1 --stream=tar --force-tar --ibbackup=/data/vadim/test-xtrabackup/xtrabackup-1.2/bin/xtrabackup ./ >> /mnt/x25m/test/3.tar
real 3m5.514s user 0m0.721s sys 0m50.415s
time ./innobackupex-1.5.1 --stream=tar --ibbackup=/data/vadim/test-xtrabackup/xtrabackup-1.2/bin/xtrabackup ./ >> /mnt/x25m/test/2.tar
real 4m56.655s user 2m44.840s sys 1m33.538s
Yes, it seems the reason is that stream uses tar4ibd in new version
Unfortunately there is not so much we can do, as tar4ibd is recommended for stream, and it is needed
to guarantee no data corruption.
time ./innobackupex- 1.5.1 --stream=tar --force-tar --ibbackup= /data/vadim/ test-xtrabackup /xtrabackup- 1.2/bin/ xtrabackup ./ >> /mnt/x25m/ test/3. tar
real 3m5.514s
user 0m0.721s
sys 0m50.415s
time ./innobackupex- 1.5.1 --stream=tar --ibbackup= /data/vadim/ test-xtrabackup /xtrabackup- 1.2/bin/ xtrabackup ./ >> /mnt/x25m/ test/2. tar
real 4m56.655s
user 2m44.840s
sys 1m33.538s