Hosting & Performance
Reading your resource usage: inodes, entry processes and I/O
Open cPanel → Resource Usage → Current Usage. These are the numbers that decide whether your site stays up under load.
Entry processes
How many PHP requests may run at the same time. This is what causes a "508 Resource Limit Is Reached" error, and it is the limit most shopping sites hit first. Twenty concurrent visitors do not need twenty entry processes — but twenty simultaneous checkouts do.
Inodes
The number of files and folders, not their size. A WordPress site with a few plugins uses about 30,000. Watch for:
- An email account with 200,000 unread messages.
- A cache or log directory that was never cleaned.
- Old backups sitting in
public_html.
Hitting the inode limit stops uploads and email delivery even when there is plenty of disk space left.
I/O and IOPS
How fast the account may read and write. Symptoms of hitting it: the site is fine when idle and crawls under load, and the admin dashboard is far slower than the public pages.
CPU
Shown as a percentage of a full core. Regularly sitting at 100% means either an inefficient plugin or a plan that is genuinely too small.
What to do about a limit you keep hitting
- Find the cause first — Metrics → Errors and the raw access log usually name it.
- Cache aggressively. Cached pages skip PHP entirely and cost almost nothing.
- Block bad bots. A scraper hammering your site consumes the same resources as a customer.
- Only then upgrade.
Ask us before upgrading. We would rather tell you that one plugin is the problem than sell you a bigger plan you do not need.