CloudLinux Resource Limits
What LVE limits are, how to check your usage in cPanel, and what to do when you hit them.
GoZen Host shared hosting runs on CloudLinux. Every account gets its own resource allocation through a system called LVE (Lightweight Virtualized Environment). This isolates your site from other accounts on the server, but it also means you have defined limits.
If your site hits a limit, it slows down or shows errors. Here’s how to monitor your usage and what to do when you’re running out of headroom.
What Gets Limited
| Resource | What It Means | What Happens When You Hit the Limit |
|---|---|---|
| CPU | Processing power available to your account | PHP scripts slow down or time out |
| Physical Memory (PMEM) | RAM your processes can use | Scripts killed with “memory exhausted” errors |
| I/O | Disk read/write speed | Slow page loads, slow database queries |
| Entry Processes (EP) | Number of concurrent PHP processes | New visitors get 503 errors while existing requests finish |
| Inodes | Maximum number of files | Can’t create new files, upload media, or receive email |
| NPROC | Total number of processes | Similar to EP but includes all processes, not just PHP |
Checking Your Usage
In cPanel
- Log into cPanel
- Go to Metrics → Resource Usage
You’ll see two views:
- Current Usage - real-time snapshot of CPU, memory, I/O, and processes
- Snapshots - historical usage over the past 24 hours, plotted on a graph
Reading the Dashboard
The dashboard shows usage as a percentage of your plan’s allocation:
| Usage Level | Meaning |
|---|---|
| 0-70% | Healthy. Plenty of headroom |
| 70-90% | Getting busy. Monitor during peak hours |
| 90-100% | Near limit. Performance will degrade under traffic spikes |
| Faults | You hit the limit. Requests were delayed or rejected |
Faults are the key metric. A fault means CloudLinux throttled your account because you exceeded a limit. Occasional faults during traffic spikes are normal. Consistent faults mean you need to optimize or upgrade.
Understanding Faults
When you see faults in the Resource Usage dashboard, here’s what each type means:
CPU Faults
Your PHP scripts are using more processing power than your plan allows. Common causes:
- Heavy WordPress plugins (page builders, SEO tools running audits)
- Unoptimized database queries
- Large file processing (image manipulation, PDF generation)
- Bots and crawlers hitting your site too frequently
Memory Faults
Your PHP processes are requesting more RAM than allowed. Common causes:
- PHP
memory_limitset too high (it allocates this per process) - WooCommerce product imports with thousands of items
- Poorly coded plugins that load entire datasets into memory
- Running multiple heavy cron jobs simultaneously
EP (Entry Process) Faults
Too many visitors are requesting PHP pages at the same time. Common causes:
- Traffic spike (legitimate or bot-driven)
- No page caching (every visitor triggers a full PHP execution)
- Ajax-heavy themes that make multiple requests per page
- WordPress heartbeat API running too frequently in the admin
I/O Faults
Your account is reading/writing to disk too fast. Common causes:
- Large database queries scanning big tables
- File operations on thousands of files (backup plugins, file managers)
- Heavy logging
Reducing Resource Usage
Quick Wins
- Enable LiteSpeed Cache - the single biggest impact. Cached pages don’t run PHP at all. See LiteSpeed Cache for WordPress
- Disable unused plugins - each active plugin adds overhead to every page load
- Block bad bots - check your access logs for aggressive crawlers and block them in
.htaccess:# Block common bad bots RewriteEngine On RewriteCond %{HTTP_USER_AGENT} (AhrefsBot|SemrushBot|DotBot|MJ12bot) [NC] RewriteRule .* - [F,L] - Optimize images - large images consume I/O and memory during processing
- Reduce WordPress heartbeat - add to
wp-config.php:define('WP_CRON_LOCK_TIMEOUT', 120); define('AUTOSAVE_INTERVAL', 300);
Deeper Optimizations
- Optimize database tables - use WP-Optimize or phpMyAdmin to clean up post revisions, spam comments, and transients
- Use a proper WP-Cron - disable WordPress’s built-in cron and use a server-side cron job instead (see Setting Up Cron Jobs)
- Audit your plugins - use the Query Monitor plugin to find which plugins are consuming the most resources
When to Upgrade
If you’ve optimized and you’re still hitting faults regularly:
- Check your plan limits - compare your usage against what your plan provides
- Consider upgrading - the next tier gives you more CPU, memory, and EP
- Consider a VPS - if you need dedicated resources without shared-hosting limits
To upgrade: log into the client area → Services → My Services → select your plan → Upgrade/Downgrade.
Upgrades are prorated. You only pay the difference for the remaining billing period.
What to Do Next
- LiteSpeed Cache for WordPress - the most impactful optimization for resource usage
- Understanding Your GoZen Hosting Stack - how CloudLinux fits into the bigger picture
- Slow Website Performance - broader performance troubleshooting
- Upgrade to VPS - no CloudLinux limits, dedicated resources
Last updated 07 Apr 2026, 00:00 +0200.