What Is a CPU Limit in Shared Hosting?

Category: Hosting Basics · Updated 2026-10-30

A CPU limit in shared hosting is a cap on how much processor time a single account can consume at any given moment, so that one busy site cannot slow down the dozens or hundreds of other sites on the same physical server. It is typically enforced automatically through a per-account container technology such as CloudLinux's LVE, expressed as a percentage of one CPU core or a number of cores.

Why CPU limits exist on shared servers

Shared hosting works by running many customer accounts on the same physical server to keep prices low. Without a cap, one account running inefficient code, handling a traffic spike, or under attack could consume most of the server's processing power, slowing down or crashing everyone else's sites. A per-account CPU limit keeps usage isolated so that no single customer can degrade the server for others.

How CPU limits are enforced

Most cPanel-based shared hosts use CloudLinux, which places each account in its own lightweight virtual environment called an LVE (Lightweight Virtual Environment). The LVE enforces limits on CPU, memory and simultaneous processes for that account alone, using the same underlying mechanism (cgroups) that containers use more broadly. When an account hits its CPU ceiling, the system throttles just that account rather than affecting its neighbors.

Typical CPU limit values

Plan tier	Typical CPU allowance
Entry shared hosting	Around 10% to 25% of one core
Mid-tier shared hosting	Around 25% to 100% of one core
Premium shared or business hosting	One or more full cores
VPS	Dedicated vCPU cores, not shared with other tenants

Signs you are hitting your CPU limit

Pages that load fine normally become noticeably slow during traffic spikes.
A control panel usage graph shows repeated spikes to 100% CPU for your account.
Error messages mentioning "resource limit reached" or a generic 503 Service Unavailable response.
Support confirms the account was briefly throttled in server logs.

Reducing CPU usage

Enable page caching so repeat visits skip rebuilding the page from scratch.
Remove or replace plugins that run heavy processing on every request.
Keep PHP and other runtimes updated, since newer versions are usually faster.
Offload images and static files to a CDN.
Upgrade to a plan, or a VPS, with a higher or dedicated CPU allowance if usage is consistently near the cap.

Frequently asked questions

What does a CPU limit in shared hosting actually control?

It controls how much processor time your account can use at any given moment, preventing one site from consuming so much CPU that it slows down other accounts on the same server.

How is a CPU limit enforced on shared hosting?

Most cPanel-based hosts use CloudLinux's LVE technology, which isolates each account and throttles only that account's processes once it exceeds its allowance.

What happens when I exceed my CPU limit?

Your site's requests may be throttled or briefly queued, sometimes showing a resource limit or 503 error, while other accounts on the server remain unaffected.

How can I tell if my site is hitting its CPU limit?

Check the resource usage section of your control panel, which often graphs CPU usage over time, or ask support to check server-side logs for throttling events on your account.

Does a CPU limit mean my site will crash?

No. A CPU limit throttles the account rather than crashing the site outright, though visitors may see slow page loads or occasional errors during the throttled period.

How do I get a higher CPU limit?

Upgrade to a higher shared hosting tier with a larger CPU allowance, or move to a VPS or dedicated server where CPU resources are reserved for your account alone.