How to read your cPanel resource graphs

The four numbers worth watching, what a healthy pattern looks like, and when to call us.

cPanel gives you resource usage graphs that most people never open. They are the fastest way to understand what your site is actually doing.

CPU

Brief spikes are normal — a page build, a cron run, a search-engine crawl. Sustained time at 100% is not. The usual culprits are an un-cached site, an aggressive bot, or a plugin doing work on every request.

Physical memory

If you are near the ceiling, something is holding too much in memory at once. Large image manipulations and unbounded database queries are the common causes.

Entry processes

This counts how many PHP requests are running simultaneously. Hitting the limit is what produces intermittent 503s for visitors while the site looks fine to you. Caching is the fix, because a cached page never starts a PHP process.

I/O and inodes

I/O is disk throughput; inodes are the number of files. A sudden inode jump usually means a plugin is writing logs or cache files and never cleaning them up. Worth finding, because it slows your backups too.

The pattern to look for

Healthy looks like low, flat usage with short spikes. Unhealthy looks like a plateau at the limit. If you see a plateau, send us a screenshot and a ticket — we can see the server side and will tell you exactly which process is responsible.