What Is an Entry Processes Limit?

Category: Hosting Basics · Updated 2026-10-30

An entry processes limit caps how many requests your hosting account can handle at the exact same moment, such as simultaneous PHP or Apache processes, regardless of how quickly each one finishes. A sudden burst of visitors, bots or slow database queries can hit this ceiling even on a site that has plenty of CPU and memory to spare, because the limit is about concurrency, not raw power.

What counts as an entry process

An entry process is any process started to handle an incoming web request to your account, most commonly a PHP or Apache worker process. Every page load that needs server-side processing opens one of these, and it stays open for as long as that specific request takes to finish. The entry processes limit, enforced through CloudLinux's LVE on most cPanel shared hosts, caps how many of these can run for your account simultaneously.

Why this limit exists separately from CPU and RAM

CPU and RAM limits control how much processing power and memory an account can use, but a site can also cause problems simply by opening too many connections at once, even if each one is lightweight. A slow database query, for example, might use very little CPU while it waits, but it still occupies an entry process slot for the whole time it is open. Capping concurrency separately protects the server from accounts that pile up many open, idle-but-waiting connections.

Typical entry processes limits

Plan tier	Typical limit
Entry shared hosting	Around 10 to 20 concurrent processes
Mid-tier or business shared hosting	Around 20 to 40 concurrent processes
Premium shared hosting	40 or more concurrent processes
VPS	Set by server configuration rather than a per-tenant cap

Common causes of hitting the limit

Sudden traffic spikes from a viral post, ad campaign or news mention.
Aggressive bots or scrapers making many rapid requests at once.
Slow database queries that keep each process open longer than normal.
Misconfigured plugins that make several internal requests per page load.
A brute-force login attempt hammering a login page with repeated requests.

Reducing concurrent process usage

Turn on full-page caching so repeat visits are served without starting a new backend process.
Switch to PHP-FPM if available, which handles concurrency more efficiently than older process models.
Put a CDN in front of static assets so image and file requests never reach the backend at all.
Block or rate-limit known bad bots and bot traffic at the firewall level.
Optimize slow database queries so each process finishes and frees its slot faster.

Frequently asked questions

What is an entry processes limit on shared hosting?

It is a cap on how many requests, such as PHP or Apache processes, your account can run at the exact same moment, independent of your CPU or RAM limits.

Why would my site hit its entry processes limit if traffic is normal?

Slow database queries, misbehaving plugins, or bot traffic can each hold a process open longer than expected, filling up your concurrency slots even without unusually high visitor numbers.

What error do I see if I hit the entry processes limit?

cPanel-based hosts on CloudLinux often show a "resource limit is reached" message or a generic 508 or 503 error for the requests that could not get a free slot.

How is an entry processes limit different from a CPU limit?

A CPU limit caps processing power used, while an entry processes limit caps how many requests can be open at the same instant, even if each one uses very little CPU while waiting.

Does caching help with an entry processes limit?

Yes, significantly. A cached page can often be served without starting a new PHP process at all, which directly reduces how many concurrent entry processes your traffic consumes.

How do I get a higher entry processes limit?

Upgrade to a higher shared hosting plan tier, which usually raises the concurrent process allowance, or move to a VPS where concurrency is limited by server capacity rather than a fixed per-account number.