CPU, RAM and disk I/O in plain words: what each one limits on your site

On shared hosting your account lives in a compartment with ceilings of its own for processor (CPU), memory (RAM) and disk reads and writes (I/O). They exist so a noisy neighbour cannot take the machine from you, and the other way round. Knowing what each does when it runs out saves a lot of time, because each fails in a different way.

The three, side by side

Resource What it is What happens at the ceiling
CPU The processing time your account may use. It runs PHP, builds pages, compresses images. It slows down. The site answers, but slowly. That is why it looks like sluggishness and not an error, and nobody suspects it.
RAM The memory your account works with at once: code, each request’s data, imports. It fails. A blank page, a critical error, an import that stops halfway.
Disk I/O The speed at which the account reads and writes files, and how many operations it does per second. It slows down. Backups, unzipping, big imports and badly managed caches are the usual culprits.

Besides these three there is the number of processes and simultaneous requests, which do not measure how heavy one thing is, they measure how many things there are at the same time. See entry processes and the limits nobody advertises.

Reading it in the panel, step by step

1 In cPanel, open Resource Usage, in the Metrics section. Depending on the limits enabled on the server, you see some or all of these graphs: CPU, memory, I/O, disk operations, processes.
2 Pick the period when the problem happened. Each graph shows usage over time against the limit, and marks the moments it hit the ceiling (the faults).
3 Compare with what was going on at that hour: an import, a backup, a campaign, a robot crawling the site. The cause almost always coincides with the peak.
4 Only then decide: fix the cause (a plugin, an image, a scheduled task) or move up a plan. See how to monitor your site performance in cPanel.
The account’s RAM is not PHP’s memory_limit. PHP’s is the most one single request may use; the account’s is the total shared by everything running at once. Raising PHP’s gives you no new resources. See PHP limits.
Where the consumption comes from is usually the site, not the plan. See what eats CPU on a website, and how to bring it down. The fast disk of a bigger plan does not fix a badly written query. On the type of disk, see SSD or NVMe storage: does the difference matter for a website.

Looked at the graphs and cannot tell what they say? Send us a screenshot of Resource Usage and we will tell you what is hitting the ceiling.

Open a support ticket

SEE ALSO

The limits nobody advertises: inodes, processes and memory

What eats CPU on a website, and how to bring it down

How to monitor your site performance in cPanel

Hosting plans

RECOMMENDED PRODUCT

Web hosting with cPanel

Domain and SSL included, daily backups and the panel you already know. from $6.59/mo (3-year plan, with coupon)

See plans
  • 0 Users Found This Useful
Was this answer helpful?