Entry Processes (EP)
Entry Processes count how many PHP scripts your account executes at the same time, not your daily visitors and not your bandwidth. Each running request takes one slot, and the slot frees again when the script finishes. A site with fast scripts and enough slots can serve many visitors without brushing the limit. What drains EP is requests that meet slow processes, not simply a busy site.
How it differs from CPU and RAM
CPU measures processor time, RAM measures memory, and EP measures process concurrency. They do not always climb together. A script can use little CPU and little RAM yet still exhaust the slots if many parallel requests pile onto it. On shared hosting, EP is usually capped by CloudLinux and shows up as its own number, separate from the disk or inode quota.
What burns slots fastest
The rough formula: EP fills when many requests meet a long processing time. Triggers include heavy plugins or themes, slow database queries that leave PHP waiting while the slot stays taken, bots hammering the login page, or a cron job hitting a heavy URL over and over. On a LiteSpeed stack the same symptom arrives as a 508 Resource Limit Reached response.
Checking your usage
In cPanel, open the Resource Usage or CPU and Concurrent Connection Usage page. An Entry Processes graph that keeps hugging the limit line marks the moments visitors see an HTTP 503 or a 508, and the process snapshot often names the stuck script. The page usually says which limit was reached, such as CPU, entry processes, memory, or IO, so you know which bar to trust. Match spikes to real activity: a cron run, an ad campaign, or a plugin you just installed.
What to do before upgrading
Fix speed first: enable caching, compress images, run a supported PHP version, and trim plugins. Filter bots with a firewall or a CDN in front of origin, then move heavy cron work off peak hours. Upgrade only if genuine human traffic still fills the graph after all that. Moving plans without cleaning up slow scripts usually just delays the next 508. The EP limit is set by the provider and varies by plan, so read the package page or ask support instead of guessing a number.
FAQ
Is the entry process limit the same on every plan?
No. The provider sets it, and it varies by plan and sometimes by account type. Check the package page or ask support; there is no universal number to assume.
Why does 508 appear and then vanish?
Because the cap is concurrent. Quiet periods pass fine, but a bot spike, a cron run, or one slow page at peak can fill the slots briefly and then clear on their own.
Does moving to a VPS remove EP?
EP caps are a CloudLinux feature of shared hosting. On a VPS you manage resources yourself and can still run out of CPU or RAM if the app is heavy, but the mechanism is different.
Disclaimer: Hosting Wiki articles are prepared for educational and reference purposes. Hosting technology keeps evolving, so some technical details may change over time.