What Resource Usage shows in cPanel
Resource Usage is a cPanel section with graphs of account resource consumption over the last 24 hours. It shows five parameters: CPU, physical memory, process count, disk I/O, and the number of simultaneous database connections. The provider sets a limit for each parameter, and when it is exceeded, the process is killed by a signal and the site returns a 500 error or hangs.
The section opens through cPanel → Metrics → Resource Usage. The graph is drawn with a one-minute step, so a short spike from a single script shows up right away.
How to read the five resource graphs
| Parameter | What it means | Typical limit |
|---|---|---|
| CPU | Share of the account's processor time | 100% of one core |
| Entry Processes | Number of simultaneous PHP processes | 20 processes |
| Physical Memory | RAM used by all of the account's processes | 1024 MB |
| I/O Usage | Disk read and write speed | 10 MB/s |
| NPROC | Total process count, including cron | 50 processes |
A red dot on the graph marks the moment the limit was exceeded. Hover over that dot — cPanel shows the exact time of the event.
How to find the script that exceeded the limit
cPanel does not keep the list of recently blocked processes for long, so match the time of the red dot against entries in the error logs. Look there for lines like these:
cpsrvd: LVE Resource limits exceeded for user: entry procs
mysqld: Too many connectionsThe limit is most often hit by heavy WordPress plugins, forgotten cron scripts that run too often, and parsers that load large files entirely into memory.
Why the Entry Processes count keeps growing
Every simultaneous visit to a site with a dynamic PHP script spawns a separate process. If a page takes a long time to respond — for example, while waiting on an external API — the process sits in memory and holds onto the limit until it finishes. As traffic grows, a limit of 20 processes runs out faster than it seems.
Caching pages and disabling unused plugins reduces the load — that is covered in the article on speeding up WordPress.
What to do about constant limit breaches
- Check the active cron jobs and their schedule in the Cron Jobs section
- Disable unused plugins and modules through the file manager
- Turn on page caching so the page is not recalculated on every visit
- Check the PHP version — an outdated version runs slower and holds a process longer
- If limits are hit steadily under normal traffic, move to a plan with higher values or to a VDS
How I/O Usage differs from Physical Memory
I/O Usage measures the speed of disk operations: reading images, writing logs, working with temporary files. Physical Memory is the RAM taken up by running processes. A script may stay under the memory limit but hit I/O while working with large files, or the reverse — hold an entire dataset in memory while barely touching the disk.
Both parameters are counted for the account as a whole, not per site, so with several domains on one account, the load from one site affects all the others.
Summary: limit diagnosis checklist
- Open cPanel → Metrics → Resource Usage and find the red dots over the last day
- Match the time of the breach against entries in error_log
- Check cron jobs, heavy plugins, and the PHP version
- Turn on caching to reduce the number of active processes
- Move to a higher plan if breaches happen regularly