How to Monitor Server Load in WHM

Monitoring server load is essential for maintaining performance and stability in a Dedicated or VPS hosting environment. WHM (Web Host Manager) provides built-in tools that enable administrators to monitor system resource usage, identify bottlenecks, and take corrective action before issues affect users.

This guide explains how to monitor server load in WHM, how to interpret load averages correctly, and what values are considered acceptable based on your server configuration.

What Is Server Load?

Server load, often referred to as the load average, represents the number of processes either actively using the CPU or waiting for CPU time. It is typically displayed as three values, which correspond to the average load over:

• 1 minute
• 5 minutes
• 15 minutes

For example:

0.45, 0.60, 0.75

These values provide insight into both short-term and long-term system activity.

How to Check Server Load in WHM

WHM makes it easy to view server load metrics through its interface.

Steps to View Server Load

1. Log in to WHM as the root user.
2. Locate the Load Averages section in the top-right corner of the WHM interface header.
   

The load average is displayed near the top of the page, along with CPU and memory usage statistics.

Understanding Load Average Values

Load averages must be interpreted in relation to the number of CPU cores available on the server.

Interpreting Load Relative to CPU Cores

Load average should be interpreted in relation to CPU cores, but it is not a direct measure of CPU utilization. On Linux systems, load average includes processes in:

• Running state (R)
• Uninterruptible sleep (D), usually waiting on disk I/O

Processes in a zombie state (Z) do not contribute to the load average.

Practical Guidelines

• A load average lower than the number of CPU cores generally indicates available processing capacity
• A load average higher than the number of CPU cores may indicate contention for CPU or other resources
• A load average equal to the number of CPU cores does not necessarily mean full CPU utilization

This distinction is important because a system can report a high load average even when CPUs are not fully utilized, especially when many processes are waiting for disk I/O (D state).

Example

If your server has 4 CPU cores:

• Load of 2.0 suggests moderate usage
• Load of 4.0 suggests the system is busy, but not necessarily CPU-bound
• Load of 6.0 or higher suggests resource contention, which could be CPU, disk I/O, or other bottlenecks

Because of this, load average should always be evaluated alongside CPU usage and disk I/O metrics rather than used as a standalone indicator.

What Is an Acceptable Load Average?

Acceptable load averages depend on both hardware and workload, but the following guidelines apply in most environments:

Healthy Range

• Load average consistently below the number of CPU cores
• Short spikes above core count are acceptable if they quickly return to normal

Warning Signs

• Load average consistently exceeding CPU core count
• Increasing trend across 1, 5, and 15-minute values

Critical Condition

• Load average is significantly higher than CPU cores for extended periods
• Accompanied by slow response times, timeouts, or service failures

It is important to evaluate load trends rather than relying on a single snapshot.

Additional Metrics to Monitor

Server load alone does not provide a complete picture. You should also review:

• CPU usage percentage
• Memory usage (RAM and swap)
• Disk I/O activity
• Running processes

These metrics are available within WHM under Server Status and Process Manager.

Common Causes of High Server Load

High load averages can result from various factors, including:

• Resource-intensive websites or scripts
• Poorly optimized databases
• High traffic spikes
• Background processes such as backups or cron jobs
• Malware or abusive processes

Identifying the root cause is essential before taking action.

Troubleshooting High Server Load

When investigating high load in WHM, it is important to correlate load averages with CPU and disk activity. Load alone does not identify the bottleneck.

Common Load Patterns and What They Mean

High load with low CPU usage

• Likely cause: disk I/O bottlenecks or processes in D state
• Symptoms: high load average, low CPU%, slow disk operations
• What to check:
  • WHM » Server Status » Daily Process Log
  • SSH tools like iostat, iotop
  • Backup jobs, large MySQL queries, or heavy disk writes

High load with high CPU usage

• Likely cause: CPU contention from active processes
• Symptoms: high load average, high CPU%, slow application response
• What to check:
  • WHM » Process Manager
  • SSH tools like top or htop
  • PHP scripts, MySQL queries, or traffic spikes

High load with idle CPU and high wait (wa)

• Likely cause: storage latency or saturation
• Symptoms: elevated I/O wait percentage, stalled processes
• What to check:
  • Disk performance and storage type (SSD vs HDD)
  • Concurrent read or write operations

Steps to Investigate

1. Check the load average in WHM.
2. Review CPU usage and I/O wait.
3. Identify top processes using WHM or SSH tools.
4. Correlate spikes with cron jobs, backups, or traffic events.
5. Optimize or reschedule resource-intensive tasks.

Best Practices for Load Monitoring

To maintain optimal performance:

• Monitor load regularly using WHM or external tools
• Set up alerts for abnormal load spikes
• Keep software and services updated
• Use caching to reduce CPU usage
• Scale resources when consistent high load is observed

Conclusion

WHM provides essential tools for monitoring server load and maintaining system health. By understanding how load averages relate to CPU cores, administrators can make informed decisions and prevent performance issues.

Consistent monitoring and proactive optimization are key to maintaining a stable, responsive hosting environment.

If you are unsure about your server’s performance limits, contact our Technical Support team for guidance specific to your hardware configuration.