diff --git a/web/app/docs/post-install/performance/page.tsx b/web/app/docs/post-install/performance/page.tsx index adb7ef7..03f5fdf 100644 --- a/web/app/docs/post-install/performance/page.tsx +++ b/web/app/docs/post-install/performance/page.tsx @@ -52,110 +52,6 @@ export default function PerformanceSettingsPage() {

Available Optimizations

-

- - Configure pigz for Faster gzip Compression -

- -

- 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:

- - /bin/pigzwrapper - #!/bin/sh - PATH=/bin:\$PATH - GZIP="-1" - exec /usr/bin/pigz "\$@" - EOF - chmod +x /bin/pigzwrapper - - # Replace gzip with pigz wrapper - mv -f /bin/gzip /bin/gzip.original - cp -f /bin/pigzwrapper /bin/gzip - chmod +x /bin/gzip - `} - /> - -

How to Use pigz

-

- 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: -

- - - -

Verifying pigz Replacement

-

- 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. -

@@ -164,42 +60,32 @@ export default function PerformanceSettingsPage() {

- 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. + This optimization replaces the default gzip compression with + pigz, a parallelized version that speeds up compression by + utilizing multiple CPU cores.

-

Why use pigz instead of gzip?

+

What does this configuration do?

    -
  • Parallel processing: Uses all available CPU cores for faster compression.
    • -
  • Faster vzdump backups: When used with Proxmox's vzdump, it reduces backup times.
    • -
  • Drop-in replacement for gzip: It works exactly like gzip but is much more efficient.
    • +
  • Forces pigz usage in vzdump backups to accelerate Proxmox VE backup compression.
    • +
  • Ensures pigz is installed before applying optimizations.
    • +
  • Creates a pigz wrapper script to enforce compression behavior.
    • +
  • Replaces gzip with the pigz wrapper, making pigz the system-wide default compressor.
-

The following steps are performed:

-
    -
  • Enables pigz in the vzdump configuration for faster backups.
    • -
  • Installs the pigz package if not already installed.
    • -
  • Creates a pigz wrapper script to replace the standard gzip command.
    • -
  • Replaces the system gzip command with the pigz wrapper.
    • -
+

How is pigz configured?

-

- Note: This optimization can significantly speed up compression tasks, especially on systems - with multiple CPU cores. -

- -

This adjustment automates the following commands:

+

This automation executes the following commands:

/bin/pigzwrapper #!/bin/sh PATH=/bin:\$PATH @@ -208,62 +94,59 @@ export default function PerformanceSettingsPage() { EOF chmod +x /bin/pigzwrapper - # Replace gzip with pigz wrapper - mv -f /bin/gzip /bin/gzip.original - cp -f /bin/pigzwrapper /bin/gzip - chmod +x /bin/gzip + # Replace gzip with pigz wrapper (backup original gzip binary) + if [ ! -f /bin/gzip.original ]; then + mv -f /bin/gzip /bin/gzip.original + cp -f /bin/pigzwrapper /bin/gzip + chmod +x /bin/gzip + fi `} /> -

How to Use pigz

+

How to Verify pigz is Active

+

- 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: + You can confirm that pigz is being used by running the following command:

+ +

+ If the output mentions pigz, the replacement was successful. +

+ +

Performance Test: gzip vs. pigz

+ +

+ To measure the speed difference between gzip and pigz, try compressing a large file: +

+ +

- The output will show that pigz completes the compression significantly faster than gzip. - To check the number of CPU cores pigz is using, run: -

- - - -

Verifying pigz Replacement

-

- 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. + Since pigz utilizes multiple CPU cores, the compression process should be significantly faster.

- By enabling pigz, compression-heavy tasks like vzdump backups and log archiving - will run much faster, leveraging multi-core processing. + With this optimization, vzdump backups and all gzip compression tasks benefit from parallel processing, + reducing execution time considerably.

+

Automatic Application