Understanding Resource Usage and Inode Limits Print

  • 0

Shared hosting plans include CPU, memory, entry-process and inode allowances. Knowing how to read them prevents surprise slowdowns.

Where to check

In cPanel, open Metrics → Resource Usage. The dashboard shows CPU, physical memory, I/O, entry processes and how often each limit was reached over the past days.

What the limits mean

  • CPU — processing power. Hitting the ceiling makes pages slow rather than offline.
  • Physical memory — RAM used by your PHP processes. Exceeding it causes 500 errors.
  • Entry processes (EP) — simultaneous PHP requests. Exceeding it shows "508 Resource Limit Reached".
  • I/O — disk read/write speed. Heavy backups or log writes can saturate it.
  • Inodes — the number of files and folders, not their size. Millions of tiny cache or session files can exhaust it long before disk space runs out.

Common causes of high usage

  • Bloated or badly-coded plugins, especially related-posts, statistics and page-builder add-ons
  • Bots and scrapers hammering the site — check Metrics → Visitors and AWStats
  • Missing caching, so every page hit rebuilds the whole page
  • Old backup archives and cached files left in the account

Reducing usage

  1. Enable a caching plugin and, where possible, server-level caching.
  2. Remove plugins you do not actively use.
  3. Optimise and compress images.
  4. Delete old backups from the hosting account; keep them locally instead.
  5. Block abusive bots and IPs with cPanel’s IP Blocker.

If your site has genuinely outgrown its plan, upgrading to a higher plan or a Cloud VPS is usually the right answer. We are happy to look at the metrics with you on a ticket.


Was this answer helpful?

« Back