import type { Metadata } from "next" import { Zap } from "lucide-react" import CopyableCode from "@/components/CopyableCode" export const metadata: Metadata = { title: "ProxMenux Post-Install: Performance Settings", description: "Guide to Performance Settings in the ProxMenux post-install script for optimizing your Proxmox VE system performance.", openGraph: { title: "ProxMenux Post-Install: Performance Settings", description: "Guide to Performance Settings in the ProxMenux post-install script for optimizing your Proxmox VE system performance.", type: "article", url: "https://macrimi.github.io/ProxMenux/docs/post-install/performance", images: [ { url: "https://macrimi.github.io/ProxMenux/performance-settings-image.png", width: 1200, height: 630, alt: "ProxMenux Post-Install Performance Settings", }, ], }, twitter: { card: "summary_large_image", title: "ProxMenux Post-Install: Performance Settings", description: "Guide to Performance Settings in the ProxMenux post-install script for optimizing your Proxmox VE system performance.", images: ["https://macrimi.github.io/ProxMenux/performance-settings-image.png"], }, } function StepNumber({ number }: { number: number }) { return (
The Performance Settings category focuses on optimizing various aspects of your Proxmox VE system to enhance overall performance. These settings are designed to improve system efficiency and speed up certain operations.
This optimization configures pigz as a faster replacement for gzip compression. Pigz is a parallel implementation of gzip that utilizes multiple CPU cores, significantly improving compression speed on modern systems.
Why use pigz instead of gzip?
The following steps are performed:
Note: This optimization can significantly speed up compression tasks, especially on systems with multiple CPU cores.
This adjustment automates the following commands:
Pigz works the same way as gzip but compresses files much faster by using multiple CPU cores. Here’s how you can test its performance:
The output will show that pigz completes the compression significantly faster than gzip. To check the number of CPU cores pigz is using, run:
After replacing gzip with pigz, you can confirm that the system is using pigz instead of gzip:
The output should show that /bin/gzip
is now linked to the pigz wrapper.
By enabling pigz, compression-heavy tasks like vzdump backups and log archiving will run much faster, leveraging multi-core processing.
This optimization configures pigz as a faster replacement for gzip compression. Pigz is a parallel implementation of gzip that utilizes multiple CPU cores, significantly improving compression speed on modern systems.
Why use pigz instead of gzip?
The following steps are performed:
Note: This optimization can significantly speed up compression tasks, especially on systems with multiple CPU cores.
This adjustment automates the following commands:
Pigz works the same way as gzip but compresses files much faster by using multiple CPU cores. Here’s how you can test its performance:
The output will show that pigz completes the compression significantly faster than gzip. To check the number of CPU cores pigz is using, run:
After replacing gzip with pigz, you can confirm that the system is using pigz instead of gzip:
The output should show that /bin/gzip
is now linked to the pigz wrapper.
By enabling pigz, compression-heavy tasks like vzdump backups and log archiving will run much faster, leveraging multi-core processing.
This performance optimization is automatically applied when selected in the Performance section. The automation ensures that pigz is correctly configured and integrated into your system, potentially improving the speed of compression operations without requiring manual intervention.