Post-Install: Performance

Settings post-install Proxmox~5 min

Performance options inside the Customizable post-install script. Currently this category contains a single optimization: replacing gzip with pigz so backups and compression use every CPU core instead of one.

What this category covers

The only performance option here rewires the system's gzip to a parallel implementation. Other performance-related tweaks (memory tuning, I/O scheduling, ZFS ARC sizing, kernel limits) live under their own categories (System, Storage) because they affect different subsystems.

Use pigz for faster gzip compression

Standard gzip compresses data using a single CPU core. On modern Proxmox hosts with 8, 16 or 32 cores, that is a huge bottleneck during vzdump VM/CT backups, log rotation, and anything else that pipes through gzip. pigz is a drop-in parallel replacement: same gzip-compatible output, but it spreads the work across every core.

What ProxMenux does

Five steps, all idempotent:

  1. Sets pigz: 1 in /etc/vzdump.conf so Proxmox's backup tool uses pigz natively.
  2. Installs the pigz apt package if not already present.
  3. Writes a wrapper script at /bin/pigzwrapper that forwards every argument to /usr/bin/pigz.
  4. Registers a dpkg diversion for the system's gzip binary (/usr/bin/gzip on Proxmox VE 9, /bin/gzip on Proxmox VE 8): the real binary is kept beside it as gzip.distrib and the wrapper takes its place. From now on, anything that calls gzip — logrotate, tar czf, scripts, vzdump — uses pigz transparently.
  5. Checks that the file kept as gzip.distrib is a working gzip before the wrapper is put in place, and reinstalls the gzip package first when it is not. A host that still has the earlier /bin/gzip.original swap is moved to the diversion when the option is applied again.
# What ProxMenux runs under the hood
sed -i "s/#pigz:.*/pigz: 1/" /etc/vzdump.conf
apt-get -y install pigz

# The wrapper pins PATH so gzip resolves inside the script even under sudo,
# and sets GZIP="-1" — fastest compression level, lowest ratio. The trade
# is intentional: on multi-core hosts wall-clock time drops far more than
# the archive grows.
cat > /bin/pigzwrapper <<'EOF'
#!/bin/sh
PATH=/bin:$PATH
export GZIP="-1"
exec /usr/bin/pigz "$@"
EOF
chmod +x /bin/pigzwrapper

# gzip is diverted: the real binary is kept as gzip.distrib, package updates
# land there, and the wrapper takes the place of gzip.
# Path on Proxmox VE 9; on Proxmox VE 8 it is /bin/gzip.
cp -p /usr/bin/gzip /usr/bin/gzip.distrib
dpkg-divert --local --no-rename --divert /usr/bin/gzip.distrib --add /usr/bin/gzip
cat /bin/pigzwrapper > /usr/bin/gzip

This replaces a system binary

Putting a wrapper in the place of gzip is unusual. It is safe (the wrapper produces gzip-compatible output), but worth knowing: scripts that hardcode paths, run inside restrictive chroots, or verify binary hashes may behave differently. The real binary is preserved as gzip.distrib, and because the replacement is a dpkg diversion, an update of the gzip package — or the upgrade from Proxmox VE 8 to 9 — updates that file and leaves the wrapper in place.

Reversible from the Uninstall menu

This optimization is tracked. Uninstall Optimizations copies the real binary from gzip.distrib back over the wrapper, removes the diversion and the pigzwrapper, comments out the pigz line in /etc/vzdump.conf, and runs apt purge pigz once gzip is verified to work. Manual equivalent on Proxmox VE 9:
# Manual rollback of pigz
cat /usr/bin/gzip.distrib > /usr/bin/gzip    # restore the real binary
dpkg-divert --local --no-rename --remove /usr/bin/gzip
rm /usr/bin/gzip.distrib /bin/pigzwrapper
sed -i 's/^pigz: 1/#pigz: 1/' /etc/vzdump.conf
# Optional: remove the package
apt purge pigz

Verification

After applying, gzip --version should mention pigz. A quick benchmark also shows the speed difference on a multi-core host:

# Confirm gzip now points to pigz
gzip --version
# Expected first line: "pigz 2.x … by Mark Adler"

# Compare throughput (create a 1GB file of random data and compress it)
dd if=/dev/urandom of=/tmp/test.bin bs=1M count=1024 status=none
time gzip -k /tmp/test.bin       # uses pigz — parallel
rm /tmp/test.bin.gz

time /bin/gzip.original -k /tmp/test.bin   # original single-threaded gzip
rm /tmp/test.bin /tmp/test.bin.gz

When this matters most

The impact scales with how many cores the host has and how often you run backups. On a 2-core home-lab box with one daily vzdump, the benefit is marginal. On a 16-core production host backing up a dozen VMs every night, pigz can cut the backup window to a fraction of what single-threaded gzip takes.

Related