Compare entry processes

Listed below is a comparison of how the 18 web host we review restrict or limit I/O.

The limit placed on entry processes by web hosts is a limit on the number of simultaneous script executions.

Websites comprise static (HTML) and dynamic content (scripts that must be executed). When you request dynamic content the request is typically sent to the server and executed by software (parser) on the server. The output of the script (HTML) is then sent back to the browser.

One example of a script execution is requesting a WordPress file (PHP). It’s important to note entry processes aren’t just defined as PHP script executions but any CGI script execution.

Limits on entry processes are also typically tied to Cloud Linux OS. Cloud Linux affords web hosts the opportunity to create what are referred to as lightweight virtualized environments (LVEs) on a Linux web server.

Each customer on a shared hosting account is typically assigned an LVE, which is basically like a “compartment” on a web server.

Each LVE is restricted to prevent any single user from disproportionately exploiting server resources, and limits on entry processes are one of many set on LVEs (others include CPU, number of processes, I/O, etc.)

The default limit set by Cloud Linux for entry processes is 20. A number of web hosts have decided to either increase or decrease the default restriction (see the comparison table above) – many more simply don’t specify how they restrict entry processes.

Entry processes shouldn’t be confused with visits or traffic. Entry processes end so quickly it’s unlikely, even with thousands of visitors on a website, that 20 users (the default limit) will create 20 entry processes at the exact same second.

It’s also important to note that entry processes are discarded as soon as they’ve completed executing.

If by some chance you do reach the entry processes threshold set by your web host then your visitors will begin receiving 508 errors (which means “resource limit reached”).