CloudLinux and LVE limits explained
Every account runs in its own container with fixed CPU, memory and process limits. What each limit does when you reach it.
Every WebGee shared and reseller account runs inside its own Lightweight Virtual Environment (LVE) — a CloudLinux container with fixed resource limits.
Why the limits exist
On shared hosting without isolation, the most common cause of downtime is one account consuming everything. A runaway script, a plugin in a loop, or a site under attack would slow the server for everyone on it.
LVE contains that. An account that exceeds its limits is throttled or has processes killed; every other account continues unaffected. The limits are not there to restrict you so much as to guarantee that someone else's problem never becomes yours.
The limits and what they do
| Limit | Symptom when reached |
|---|---|
| CPU | The site slows down. Requests still complete |
| I/O | The site slows down, especially anything disk-heavy |
| Entry processes (EP) | 503 error — requests are killed outright |
| Physical memory (PMEM) | 503 error, or the process is killed |
The distinction matters when diagnosing. CPU and I/O limits degrade; EP and memory limits break. A site that has become sluggish is hitting a different limit from one returning 503s.
Where to see it
cPanel → Resource Usage shows which limits were reached and when. When an account hits a limit, a snapshot records which processes were responsible — that snapshot is what tells you the cause rather than just the symptom.
What to do about it
Almost always the answer is at application level, not the plan:
- Cache. A cached page consumes almost nothing.
- Audit plugins. Disable all, re-enable one at a time watching Resource Usage.
- Fix cron schedules. Heavy jobs on short intervals are a frequent cause.
- Check for malware. A compromised site consumes resources doing someone else's work — see Scan your site for malware.
If usage is genuinely legitimate, the limits can be raised. Open a ticket with your Resource Usage figures.
Related
Fix the Redis "OOM command not allowed" error
Redis has its own memory limit, separate from your account's. When the cache fills, writes fail with this error until it is cleared or raised.
What entry processes are
Entry processes count requests being handled simultaneously, not visitors. Why a slow site hits the limit long before a fast one does.