---
title: Entry Processes (EP)
description: A concurrent PHP process limit on shared hosting. Often behind Error 508 — not a daily visitor cap.
canonical: https://penasihathosting.com/en/hosting-wiki/entry-processes-ep
type: wiki
locale: en
updated: 2026-07-15
author: Willya Randika
---

# Entry Processes (EP)

## Overview

- **Summary:** A concurrent PHP process limit on shared hosting. Often behind Error 508 — not a daily visitor cap.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

Ever opened your own site and hit a white page that says **"508 Resource Limit Is Reached"**? That usually is not “you got hacked” or “a million visitors arrived overnight.”

More often it is **Entry Processes (EP)**: how many PHP processes may run **at the same time** on a shared account (common on CloudLinux + [cPanel](/en/hosting-wiki/cpanel)).

## EP Is Not a Daily Visitor Cap

EP measures **concurrency**, not total visitors per day.

- A healthy script finishes in milliseconds, then frees its EP slot  
- A limit of **20 EP** means about 20 PHP requests *truly at once*, not 20 people all day  
- A slow site holds the “cashier” longer — slots fill even with modest traffic  

Shared plans often sit around **20–50 EP**, depending on the package.

## Supermarket Cashier Analogy

- **Shoppers in the store** = traffic (can be many)  
- **Cashiers** = Entry Processes  
- **Queue meltdown** = Error 508  

Hundreds of people can browse. Trouble starts when cashiers are few **and** each checkout is slow (heavy scripts, slow database, bots hammering login).

Rough idea:

> **Full EP ≈ many requests × long processing time**

## Common Causes of 508

1. **Heavy plugins/themes** or jobs that hold PHP open  
2. **Bots / brute force** (wp-login, xmlrpc)  
3. **Cron** work during peak hours  
4. **Slow database queries** — PHP waits while the EP seat stays occupied  

## How to Check in the Panel

1. Sign in to cPanel  
2. Open **Resource Usage** / **CPU and Concurrent Connection Usage**  
3. Inspect the **Entry Processes** graph and process snapshots  

Charts that hug the limit line map to moments visitors see 508. Snapshots often name the stuck script.

## What to Do Before You Upgrade

1. **Speed the site up** — cache, image compression, supported PHP, fewer plugins  
2. **Filter bots** — firewall, rate limits, a [CDN](/en/hosting-wiki/cdn)/Cloudflare in front of origin  
3. **Schedule heavy cron** off-peak  
4. **Upgrade** only if real human traffic still saturates EP after cleanup (higher cloud/VPS limits)  

Upgrading without fixing slow scripts often just delays the next 508.

## What to Watch For

- A low EP number is **not** automatically a bad plan; a lean site on 20 EP can serve thousands of daily visits  
- 508 signals a **slow kitchen or a rush**, not only “buy expensive hosting”  
- Recheck resources after new plugins or ad campaigns  

## FAQ

<Accordion>
  <AccordionItem title="Is 20 EP enough for a small store?">
    Yes if pages are fast and bots are controlled. Flash sales or heavy ad traffic may need more headroom — optimize first, then upgrade if graphs still fill with real users.
  </AccordionItem>
  <AccordionItem title="How is EP different from bandwidth or inodes?">
    [Bandwidth](/en/hosting-wiki/hosting-bandwidth) is data transfer. [Inodes](/en/hosting-wiki/inode) are file counts. EP is concurrent PHP work. Three separate limits.
  </AccordionItem>
  <AccordionItem title="Why is 508 only intermittent?">
    The limit is concurrent. Quiet periods pass. A bot spike, cron run, or slow page at peak fills slots briefly, then clears.
  </AccordionItem>
  <AccordionItem title="Does a VPS remove EP entirely?">
    CloudLinux-style EP caps are typical of shared hosting. On a VPS you manage resources yourself — you can still exhaust CPU/RAM if the app is heavy, but the mechanism differs.
  </AccordionItem>
</Accordion>