Applies to: cPanel clients, cPanel resellers (WHM), and servers running CloudLinux with LVE on both cPanel and Plesk (managed & unmanaged).
What CloudLinux + LVE Does
On shared and reseller servers, one busy or misconfigured site can consume excessive resources and impact everyone. CloudLinux with LVE (Lightweight Virtual Environment) isolates each hosting account (or Plesk subscription) into its own resource “silo.” If a site exceeds its limits, that site may slow or error, while other sites on the server remain stable.
- LVE provides per-account limits for CPU, memory, entry processes (EP), disk I/O, etc.
- Goal: prevent “noisy neighbors” from degrading server performance.
- Scope: limits primarily affect web/PHP workloads; email delivery is generally not limited by LVE.
- HTTP 508 Resource Limit Reached (most common)
- HTTP 500 errors or intermittent slow responses during spikes
- Red “fault” markers in Resource Usage graphs (CPU, Memory, IO, EP)
The Main Limits (and what they mean)
| Limit | What it controls | Typical defaults* | Notes |
|---|---|---|---|
| CPU | Share of core(s) available to the account | 100–200% | 200% ≈ two cores worth of time slice. |
| PMEM | Physical RAM for PHP/app processes | 1–2 GB | If exceeded, processes may be killed. |
| EP (Entry Processes) | Concurrent web/PHP entries (not “visitors”) | 20–40 | Short-lived; 20 EP often handles 70–100 concurrent users on typical WP. |
| IO | Disk throughput per account | 5–10 MB/s | Low IO appears as “slowness” on file ops. |
| IOPS | I/O operations per second | 1,024+ | Helps with many small reads/writes. |
| NPROC | Total processes owned by the user | 100–200 | Prevents runaway process trees. |
| MySQL I/O | DB engine rate limiter | Varies by host | High caps (e.g., “1.86 GB/s”) are limits, not guaranteed throughput. |
| Inodes | Total files/directories owned | Often high or unlimited | Large caches/backups can exhaust inodes. |
*Exact defaults vary by plan and server build. Your plan’s limits apply.
Is EP the same as “number of visitors”?
No. EP counts concurrent PHP “entries,” not people. Because each request is usually fast, 20 EP often supports dozens of active visitors. Constantly maxed EP usually points to slow PHP, heavy plugins, slow DB queries, or bot spikes.
How to Check Your Usage
cPanel (End-User)
- Log in to cPanel.
- Open Metrics → Resource Usage.
- Review graphs for CPU, Memory, IO, EP and any Faults (limits hit).
WHM (Resellers / Admins on cPanel)
- Log in to WHM.
- Open CloudLinux / LVE Manager.
- Use Current Usage / Statistics to find accounts hitting limits.
Plesk (End-User & Admin)
- Log in to Plesk.
- Go to Websites & Domains → Resource Usage for your subscription.
- Admins can use the CloudLinux/LVE extension to inspect usage.
Policy & Next Steps
- Shared hosting & resellers: If you frequently hit limits, consider site optimisation (page/object caching, image/WebP, plugin audit, bot controls). If usage is legitimately high, upgrading your plan/package is recommended.
- Unmanaged servers (root access): You can adjust limits in LVE Manager (WHM/Plesk) or via CLI (
lvectl), and tune PHP/OPcache/DB as needed. - How to upgrade/adjust: See our companion article: Upgrading LVE Resources for cPanel & Plesk Accounts .
FAQ
Will email stop if my site hits LVE limits?
No—LVE targets web/PHP workloads. Mail flow issues are usually unrelated to LVE limits.
Why do I see 500 vs 508?
Both can occur depending on the PHP handler and which limit was hit. 508 is the canonical “Resource Limit Reached.”
Are the defaults enough?
For most small–medium WordPress sites, defaults such as 1–2 GB RAM, 100–200% CPU, 20–40 EP, 5–10 MB/s IO are sufficient. Busy stores or heavy plugins may need more.
References
Last updated: September 2025
