> ## Documentation Index
> Fetch the complete documentation index at: https://speedypage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor resource usage

> How to check CPU, memory, I/O, and process usage for your cPanel account using the CloudLinux resource usage interface.

Every SpeedyPage Web Hosting and WordPress Hosting account runs on CloudLinux with per-account resource limits enforced by LVE (Lightweight Virtual Environment). The Resource Usage page in cPanel shows how much of each limit you're actually using.

## Open resource usage

Log in to cPanel through your [client area](https://my.speedypage.com) or at `yourdomain.com/cpanel`. Go to **Metrics** and click **Resource Usage** (also labelled **CPU and Concurrent Connection Usage**).

## What each metric means

| Metric              | What it measures                                                                                                                                   |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| CPU                 | Processor time your account has used. Measured as a percentage of your allocated CPU cores.                                                        |
| Physical memory     | RAM consumed by your account's processes. Includes PHP workers, MySQL connections from your scripts, and any running cron jobs.                    |
| I/O (throughput)    | Disk read/write speed in MB/s. High I/O usually comes from database queries or large file operations.                                              |
| IOPS                | Number of individual disk read/write operations per second.                                                                                        |
| Entry processes     | Concurrent connections entering your account — each PHP request, SSH session, or cron job counts as one. This is the most common limit people hit. |
| Number of processes | Total processes running under your account at any point, including background tasks and child processes spawned by PHP.                            |

## Reading the graphs

The interface shows two types of data for each metric:

* **Current usage** — a real-time snapshot of how much of the resource your account is consuming right now.
* **Faults** — the number of times your account hit the limit during the selected time period. Each fault means a request was delayed or denied because the limit was reached.

You can view data for the past 24 hours, the past week, or the past month. A small number of occasional faults is normal during traffic spikes. Sustained or frequent faults mean your account is regularly exceeding its limits.

## What to do when you're hitting limits

If you're seeing faults regularly, here are the most common fixes:

**High entry processes or number of processes**

* Enable LiteSpeed caching (LSCache) if it's not already active. This reduces the number of PHP processes needed to serve your site.
* Check for slow PHP scripts or plugins that keep connections open longer than necessary.
* Make sure cron jobs aren't overlapping — a job that takes longer than its schedule interval will stack up processes.

**High CPU usage**

* Look for unoptimized database queries, especially on WordPress sites with many plugins.
* Disable plugins you're not actively using.
* Use object caching to reduce repeated processing.

**High memory usage**

* Lower the PHP memory limit per script if you've set it higher than needed.
* Check for memory leaks in custom code or poorly written plugins.

**High I/O or IOPS**

* Enable database query caching.
* Reduce the frequency of cron jobs that read or write large amounts of data.

<Tip>
  See [resource limits](/web-hosting/resource-limits) for the exact CPU, memory, and process limits on each plan tier. If you've optimized your site and still hit limits, upgrading your plan is the next step.
</Tip>

<Warning>
  When your account reaches its entry process limit, new visitors see 503 errors until existing connections finish. This is the single most common cause of intermittent downtime on shared hosting.
</Warning>