Understanding LVE Resource Limits

Every account on our servers runs inside a CloudLinux Lightweight Virtual Environment, or LVE. The LVE gives your site a guaranteed share of the server's resources and keeps a busy neighbor from slowing you down. This guide explains each limit in plain terms and how to keep your site inside them.

What an LVE Is

Our servers run cPanel on CloudLinux. CloudLinux wraps each hosting account in its own LVE — a small, isolated container with defined ceilings for CPU, memory, and other resources. Because every account has its own LVE, one site that suddenly gets busy cannot consume the whole server and take everyone else down with it. Your plan sets the size of your LVE.

The Limits Explained

An LVE has several limits, each measuring a different kind of activity:

CPU (%) — how much processor time your site may use, expressed as a percentage of a core. PHP execution, database queries, and heavy plugins all consume CPU. This is the limit busy sites hit most often.
Physical Memory (PMEM) — the RAM your processes may use at once. Hitting it can cause a script to be killed mid-request, which visitors see as an error.
Entry Processes (EP) — the number of requests being actively processed at the same instant. Each page that is mid-render counts as one entry process. This is not total visitors, but how many are being served simultaneously right now.
Number of Processes (NPROC) — the total processes your account may have running, including PHP workers, cron jobs, and shell sessions.
IO and IOPS — IO is the rate at which your site reads and writes data (throughput), and IOPS is the number of separate read/write operations per second. Sites that log heavily or shuffle many small files lean on these.

Note Entry Processes is the limit people most often misread. A visitor who loads a page and reads it does not hold an entry process — only the split second the server spends generating the page does. Slow pages hold entry processes longer, which is why speeding up your site lowers EP usage.

Reading the Resource Usage Graphs

Log into cPanel.
In the Metrics section, click Resource Usage.
The overview tells you at a glance whether you have hit any limit recently. Click Details (or Snapshot) to see per-resource graphs.
Choose a resource and a time range. On each graph, the line is your usage and the shaded ceiling is your limit. Where the line touches the ceiling, you were capped.

What "Faults" Mean

A fault is recorded each time your account hits a limit and CloudLinux has to throttle it. A CPU fault means requests were slowed while waiting for processor time; an EP fault means a visitor briefly could not be served because all your entry process slots were full; a memory fault means a process was stopped for using too much RAM.

Warning Occasional faults during a traffic spike are normal and harmless. But frequent faults mean visitors are seeing slow pages or errors. If your graphs show sustained faults, treat it as a signal to reduce usage or move to a larger plan.

Common Causes of High Usage

Traffic spikes — a burst of real visitors, a marketing campaign, or being linked from a busy site.
Heavy plugins and themes — poorly written or excessive plugins that run a lot of code on every page.
Bots and scrapers — aggressive crawlers and bad bots that hammer your site far harder than humans do.
No caching — rebuilding every page from scratch on every request, instead of serving a cached copy.
Inefficient database queries — slow or unindexed queries that tie up CPU and IO.

Reducing Usage or Upgrading

Most sites can comfortably stay within their limits with a few changes:

Enable caching — a full-page cache serves ready-made HTML and cuts CPU and EP usage dramatically. See AccelerateWP for WordPress.
Optimize your database — add indexes, remove bloat, and clean up expired data so queries run faster.
Trim plugins — remove or replace heavy plugins and keep everything updated.
Block bad bots — stop abusive crawlers so real visitors get your resources.

If you have tuned your site and still hit your limits regularly, your traffic has simply outgrown the plan. Plan limits are enforced, and the way forward is to reduce usage or upgrade — support does not raise LVE limits to bypass them. See Resource Limits for a broader overview, and Resource Limit Reached (508 errors) if visitors are being turned away. When you are ready to upgrade, open a support ticket and we will help you pick the right plan.