From 123d95ec47309bcbbd9555df489d444b61a3c014 Mon Sep 17 00:00:00 2001 From: MacRimi Date: Sun, 2 Mar 2025 12:46:02 +0100 Subject: [PATCH] Update --- .../docs/post-install/basic-settings/page.tsx | 112 ++++++++++++++++++ web/app/docs/post-install/system/page.tsx | 53 ++++----- 2 files changed, 133 insertions(+), 32 deletions(-) diff --git a/web/app/docs/post-install/basic-settings/page.tsx b/web/app/docs/post-install/basic-settings/page.tsx index 9311f0d..508cbf2 100644 --- a/web/app/docs/post-install/basic-settings/page.tsx +++ b/web/app/docs/post-install/basic-settings/page.tsx @@ -65,6 +65,95 @@ export default function BasicSettingsPage() { VE system. They provide essential tools for monitoring system performance, managing files, and troubleshooting issues, enhancing your ability to maintain and optimize your virtualization environment.

+

Utilities installed:

+

This adjustment automates the following command:

+

Repository changes:

+

This adjustment automates the following command:

System Settings

- The System Settings category focuses on core system configurations and optimizations for your - Proxmox VE installation. These settings are crucial for improving system performance, stability, and resource - management, ensuring your virtualization environment operates at peak efficiency. + The System Settings category includes core system configurations and optimizations for Proxmox VE, + focusing on performance, stability, and resource management.

Available Optimizations

@@ -57,13 +56,12 @@ export default function SystemSettingsPage() { Enable Fast Reboots

- This optimization enables kexec, a mechanism that allows the system to boot directly into a new - kernel from an existing running kernel, bypassing the BIOS/firmware and bootloader stages. + This optimization enables kexec, allowing the system to boot directly into a new kernel + without going through the BIOS/firmware and bootloader.

- Why it's beneficial: Fast reboots significantly reduce system downtime during maintenance or - updates. In a virtualization environment where multiple VMs might be running, minimizing host downtime is - crucial for maintaining high availability and reducing disruption to services. + Why it's beneficial: FFast reboots reduce system downtime during updates and maintenance. + This is particularly useful in virtualization environments where minimizing host downtime helps maintain service availability.

This adjustment automates the following commands:

> ~/.bash_profile Configure Kernel Panic Behavior

- This setting configures the system to automatically reboot after a kernel panic occurs, rather than hanging - indefinitely. + This setting configures the system to automatically reboot after a kernel panic instead of remaining unresponsive.

- Why it's beneficial: Automatic reboots after kernel panics help maintain system availability. - Instead of requiring manual intervention, which could lead to extended downtime, the system attempts to recover - on its own. This is particularly crucial in remote or lights-out data center environments where immediate - physical access might not be possible. + Why it's beneficial: AAutomatic recovery reduces downtime and prevents the need for manual intervention, + which is critical in remote or unattended environments where physical access is limited.

This adjustment automates the following commands:

- This optimization increases various system limits, including the maximum number of file watches and open file - descriptors. + This optimization increases system resource limits, including the maximum number of file watches and open file descriptors.

- Why it's beneficial: Higher system limits allow for better resource utilization, especially in - high-density virtualization environments. Increased file watch limits improve performance for applications that - monitor many files (like backup systems or development environments). Higher open file limits allow more - concurrent connections and file operations, which is crucial for busy servers hosting multiple VMs or - containers. + Why it's beneficial: Higher limits enhance resource utilization, improving performance for applications + that monitor large numbers of files or handle high concurrent connections. This is essential + for servers running multiple VMs or containers.

This adjustment automates the following commands:

- This setting configures systemd's journald logging service to limit its disk usage and optimize performance. + This setting configures systemd-journald to limit disk usage and optimize logging performance.

- Why it's beneficial: Proper log management is crucial for system health and troubleshooting. By - limiting the maximum size of the journal, you prevent logs from consuming excessive disk space, which could - potentially fill up the system partition. This is especially important in virtualization environments where disk - space is often at a premium. Additionally, optimized logging reduces I/O operations, potentially improving - overall system performance. + Why it's beneficial: Restricting log size prevents excessive disk consumption, + reducing the risk of system partitions filling up. Optimized logging also decreases I/O operations, + improving system performance, especially in disk-constrained environments.

This adjustment automates the following commands:

- This optimization adjusts various memory-related kernel parameters to improve system performance and stability. + This optimization adjusts kernel parameters to improve memory allocation and system responsiveness.

- Why it's beneficial: Proper memory management is critical in virtualization environments where - multiple VMs compete for resources. These optimizations can help prevent out-of-memory situations, improve - memory allocation efficiency, and enhance overall system responsiveness. This is particularly beneficial for - hosts running memory-intensive workloads or a high number of VMs. + Why it's beneficial: Efficient memory management prevents out-of-memory (OOM) conditions, + enhances stability, and optimizes resource allocation in virtualization environments. + This is particularly important for hosts running memory-intensive workloads or multiple VMs.

This adjustment automates the following commands: