Replies: 2 comments
-
Here some examples from my server:
Using pigz:
Bonus - using zstd (zstdmt):
The actual code: compression_time=`/usr/bin/time -f "* Total compression time: %e seconds with %P CPU usage" \
tar -I zstdmt -cf "${backupdir}/${backupname}.tar.zst" \
-C "${rootdir}" --exclude "${excludedir}" --exclude "${lockdir}/backup.lock" ./. \
2>&1 > /dev/null` |
Beta Was this translation helpful? Give feedback.
0 replies
-
To close the loop on this. Looks like it was implemented: #4509 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello.
Pigz compresses using threads to make use of multiple processors and cores.
I've made my own local changes utilizing pigz for backups instead of gzip in this script.
examples:
tar --use-compress-program=pigz
tar cf - paths-to-archive | pigz -9 -p 32 > archive.tar.gz
This could possibly benefit more users, speeding up the backup process. It helps a lot for me.
Maybe even enable options for describing how many cores to use?
What do you think?
PS: there are some more examples here:
https://stackoverflow.com/questions/36917882/how-to-use-pigz-with-tar
Beta Was this translation helpful? Give feedback.
All reactions