Speed Up File Compression with Pigz: Parallel GZip Implementation

Joe BordesJoe Bordes
2 min read

I learned about pigz today. While reviewing the processes in one of my Linux servers I saw this process eating up the CPU resources and immediately thought it was some cryptocurrency mining hack. After some investigation, I found a VERY nice tool!

From the manual page:

Pigz compresses using threads to make use of multiple processors and cores. The input is broken up into 128 KB chunks with each compressed in parallel. The individual check value for each chunk is also calculated in parallel.

So a gzip that uses all the processors in the server to do its work faster. Let's give that a try.

I look around the server and find a 14Gb SQL dump file of one of our databases. It's a perfect file for a compression test. So I compress and uncompress it with pigz and gzip.

time pigz cbcrm_pre_update_30052024.sql
time unpigz cbcrm_pre_update_30052024.sql.gz
time gzip cbcrm_pre_update_30052024.sql
time gunzip cbcrm_pre_update_30052024.sql.gz

The results:

CommandRealUserSystem
pigz1m54.518s1m18.354s0m13.380s
unpigz1m38.363s0m49.843s0m20.917s
gzip4m6.779s3m53.000s0m8.151s
gunzip1m37.684s0m59.503s0m7.100s

The time for compression has a significant difference, while the uncompression is almost similar, I suppose due to the complexities of creating meaningful chunks of compressed data and the internals of the gzip format.

The htop output shows a clear difference in server resource usage:

These first two images are two different moments of the pigz execution:

where we clearly see all CPUs working together. The next two images are for the gzip execution.

where we see the lack of parallel computing. The unzip executions look similar.

In the Altlantic article referenced below and in the manual you will find some useful execution options and combinations.

A very practical use of programming and server knowledge! Kudos to the pigz team.

References

0
Subscribe to my newsletter

Read articles from Joe Bordes directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Joe Bordes
Joe Bordes