CloudLinux Resource Limits
What LVE limits are, how to check your usage in cPanel, and what to do when you hit them.
4 min read
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. This article covers 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 | Processes are killed and visitors see 500 or 508 errors |
| I/O | Disk read/write speed | Slow page loads, slow database queries |
| Entry Processes (EP) | Number of concurrent PHP processes | New visitors get a “508 Resource Limit Is Reached” error until running 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
Each fault type in the Resource Usage dashboard points to a different cause:
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:
- Scripts that legitimately use a lot of memory (a high
memory_limitlets one runaway script use more before it is stopped) - 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 autosave frequency - add to
wp-config.php(seconds between editor autosaves):define('AUTOSAVE_INTERVAL', 300); - Limit the WordPress Heartbeat API - in LiteSpeed Cache > Toolbox > Heartbeat, or with the
heartbeat_settingsfilter
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
- Free Migration - if the upgrade also means switching hosts, we handle the move at no charge
Last updated 21 Oct 2026, 00:00 +0300.