Understanding shared hosting resource limits
Shared hosting has CPU, RAM, process, and disk limits enforced by CloudLinux. Learn what each limit means, how to check your usage,
UnderHost NOC
Network Operations
On this page
UnderHost shared hosting uses CloudLinux to enforce per-account resource limits. These limits protect all accounts on the server-if one account uses excessive resources, it cannot affect others. Understanding them helps you keep your site running smoothly.
What limits exist
| Resource | What it measures | Typical effect when exceeded |
|---|---|---|
| CPU | Processing power used by PHP, scripts, and cron jobs | Pages load slowly; processes are throttled |
| RAM (PMEM) | Memory used by PHP processes | PHP processes are killed; 500 errors or blank pages |
| Entry Processes (EP) | Simultaneous PHP requests executing at once | New visitors see 508 Resource Limit Reached |
| I/O | Disk read/write speed | File access slows; queries take longer |
| Disk space | Total storage used by files, email, databases | Cannot create new files or receive email; 500 errors |
| Inodes | Number of files and directories | Cannot create new files even with disk space remaining |
How to check your usage
- Log in to cPanel
- Go to Metrics → Resource Usage (or search "Resource Usage" in cPanel)
- View current and 24-hour usage graphs for CPU, RAM, EP, and I/O
Disk space and inode usage are shown in the cPanel sidebar under your account name at the top.
When you hit limits
Limits are soft throttles, not hard cuts-the server tries to keep your site running at reduced speed before failing. Common symptoms:
- 508 Resource Limit Reached-too many concurrent PHP processes (EP limit)
- 500 Internal Server Error-PHP process killed by RAM limit
- Very slow page loads-CPU throttling
- Cannot upload files / email bounces-disk full or inode limit
How to reduce usage
- Enable caching-a WordPress caching plugin (WP Super Cache, W3 Total Cache) reduces PHP execution per visit dramatically
- Optimize images-large images increase I/O and disk usage
- Clean up email-old mailboxes storing thousands of messages use disk and inodes
- Remove unused plugins and themes-inactive plugins still add files
- Limit cron jobs-frequent cron jobs spike CPU usage
- Check for runaway scripts-a poorly coded plugin can consume all CPU
When to upgrade to VPS
If your site is legitimately exceeding limits despite optimization, shared hosting has reached its ceiling. A Cloud VPS gives you dedicated CPU and RAM with no sharing, suitable for high-traffic sites, WooCommerce stores, and custom applications. See the Shared vs VPS comparison.
Related: CloudLinux overview | CloudLinux resource limit | Shared hosting overview | Upgrade account
Need shared hosting?
Choose an UnderHost shared hosting plan with cPanel, email, SSL, DNS tools, and 24/7 support.
