If you would like to subscribe to a shared hosting package, you need first to understand what are the specifications the hosting provider offers for a certain package. One of them is the entry processes limit in the shared hosting.
Usually, the Entry Processes of a kind of Managed WordPress Hosting is really capable to handle a great deal of web traffic. But commonly shared hosting providers offer an Entry Process Limit in the range from 10 to 25. In contrast, a Managed WordPress Hosting can be greater than 25, which is around 30 or even up to 800 Entry Process.
A WordPress Hosting package usually requires that much because the server has no good protection against DDoS attack and Fake (Spam) Traffic.
Should You Need an Entry Process Limit More Than 20?
Today, shared hostings or non-managed WordPress hostings that use CloudLinux Server Operating System commonly provide an entry process limit up to 20. In which, it’s a standard number based on CloudLinux’s Best Practice recommendation (Research). 20 is the ideal number for an entry process limit. There are even some hosting providers provide below 20.
What is Entry Processes Limit (EP)?
Entry Processes Limit means a control of the maximum number of entries into Lightweight Virtual Environment (LVE). It means the increase of the EP counter depends on every single visitor or process that enters into LVE. And the decrease of the EP counter depends on every visitor or process exits LVE. But CloudLinux will not count any process that is generated inside the LVE itself. Because an LVE restricts the number of resources such as the CPU, I/O and RAM of a hosting package.
In other words, the entry processes limit of a web hosting is the maximum number of simultaneous running processes that a hosting account is capable of handling. And it’s onerous to gauge the number of traffic this would correspond to because it relies on your blog or site and any scheduled tasks you are running. For instance, when a visitor loads a PHP page of you do a cron job on your site, the PHP or any activity whip up is started and it would normally be ended right away. It’s unlikely your site is getting so many visitors simultaneously. in which such condition makes your entry process gets a technical problem.
Generally, the process of an entry only takes about a fraction of a second to complete. So, if the entry process limit of your shared hosting is 20, it means 20 visitors can open your blog simultaneously in a split second. When your site hits the limit, any visitor that requests an access to will see an error notification until there are less than 20 processes on your website. But, it’s very rarely found a blog is getting 20 visitors in a split second simultaneously. Therefore, if you are only going to start a new blog or site, a 20 entry processes limit shared hosting is more than enough.
CloudLinux is the most popular Operating System for Shared Hostings because it has already a Semi-VPS with its virtualization capabilities. While the Entry Process is one of the CloudLinux configurations for the Lightweight Virtual Environment (LVE) feature. Simply, an entry process means a process of an entry into LVE for every HTTP request for PHP/CGI.
Read also; Cloud Hosting vs Shared Hosting
Many people mistakenly interpret Entry Process as a Limit of Visitors who are opening a website at the same time. It isn’t. Because after a Process has been ended, or the whole webpage has been downloaded, a good Script should do a “Release” and “Kill” process depends on its entry processes availability, so as not to become a “Zombie Process”. In this case, WordPress, Joomla, and Drupal CMSes are really good at doing so.
Many times hosting providers use a gimmick of Entry Process Limit by connecting it to the huge potential of WordPress Plugins.
While in fact, a problem of entry process limit usually arises on PHP Scripts created by the Web Developers who build a Website based on PHP from nothing (manual coding). Many of them lax in script optimization, including entry process limit. An entry process limit may also arise when you run a lot of PHP processes using cron jobs.
But lets we focus on CMS users, specifically self-hosted WordPress blog. Many bloggers dilemma when they just knew that a Managed WordPress Hosting providers make a huge number of their Entry Process Limit as an excellence.
New bloggers would like crazy when they see a high specification of a web hosting. Newbies would be easily outwitted. But I am sure that a new WordPress blogger wouldn’t need a huge number of entry processes limit, which is no more than 20. Even for a blog with a huge amount of daily traffic. Whereas, the CPU and Physical Memory Usage of a web hosting will be more proportionate with a huge amount of web traffic.
Why Hosting Providers Limit the Entry Processes of a Shared Hosting
The entry processes limit is crucial to prevent DoS attacks towards a web server. And another type of common attack, which is to tie up the entire Apache connections by whacking a number of slow pages on the server. When the entire slots of the Apache are used up, people cannot connect to the server. This makes the site look down. Such problem is degenerated by the CPU limit. If a website gets slow due to its server’s CPU limit, all of its HTTP requests are getting slower, which leads more Apache connections to be tied up.
So, the entry processes limit is a solution to solve preventing DoS attacks and other web-based attacks. Entry processes limit is also called as concurrent connections limit. This configuration will restrict how many simultaneous connections to Apache are allowed. The web server will serve error 508 page when the number of simultaneous requests to the blog goes over the entry processes limit.
But what if the lots of HTTP requests are real visitors, not DoS (fake traffic)? That’s a good question! The 20 entry process limit is almost impossible to get exhausted those requests are normally real visitors or customers. Take note that, the 20 process limit of a Linux shared hosting is based on the best practice of CloudLinux experience so far, which is assumed for a normal website, optimized, and real traffic from humans.
Take note that, the 20 process limit of a Linux shared hosting is based on the best practice of CloudLinux experience so far, which is assumed for a normal website, optimized, and real traffic from humans. So, bloggers need to use a quality web hosting service which supports a security hardening feature that resolves DDoS and Spam issues.
Finally, the entry process is hardly ever described on the general purpose of a shared hosting, nor in the web hosting service preview page, as it isn’t crucial. So, find out how good a web hosting service is and what are its specifications, whether or not they fit your needs.