While this doesn't directly address the issue you're experiencing, it may help slightly. In my Proxmox deployments, I've replaced /bin/gzip with pigz ( http://zlib.net/pigz/ apt-get install pigz ; ln -sfb /usr/bin/pigz /bin/gzip). pigz is a multi-threaded gzip, and it significantly decreased our backup times by speeding up the compression. We saw backup times drop to just 10-50% of what they took running gzip. These big, beefy virtualisation servers have all these CPUs+cores, so why limit gzip to just one?
-- Bryce Chidester Director of Systems Engineering Calyptix Security | Simply Powerful Network Security. www.calyptix.com On Sun, 2015-07-05 at 21:19 +0200, Tonči Stipičević wrote: > Hello to all > > I'm using 4xIntelAtom CPU 2558 @2,4GHz on the host > a backup storages are (1G) freenas nfs and local sata disk > > So classic backup (vzdump) of 32G image takes about 1h ... the same > result to the nfs storage and to local sata disk > I tried changing bwlimit in vzdump.conf the result is allways the > same slow > > But Clone VM takes less then 10 min > > manual lzop backup of this image (nfs storage or sata disk) takes > less than 10' too ... tar runs same fast > > So we cannot say tha CPU is not capable of doing archiving with > commpression > > Why is backup so slow and what can I do to optimize it? > > thank you very much in advance and > BR > > Tonci > _______________________________________________ > pve-user mailing list > [email protected] > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
