Options for when you’re exceeding PHP worker limits

There are a couple of ways your site can be running out of resources. One of the common ones we hear a lot about is about a site exceeding PHP worker limits. And we think it’s a little bit silly to be having this problem in the first place. Let me explain.

What are the PHP worker limits at Servebolt?

Let’s start with explaining what a PHP worker is first before I answer this question. PHP, as a programming language is a single-threaded interpreter by design in its core. PHP workers determine how many simultaneous requests server can execute at a given time. Requests are executing almost instantly.

Questions like “How many PHP workers do I need?” or “What if workers are not enough?” are common questions asked if your site is indeed limited by a fixed amount of workers. At Servebolt, your site is not limited by PHP workers.

Here’s why. The worker limit is something that comes by design from PHP-FPM, the FastCGI Process Manager used by many hosting companies. In our stack we deal with workers dynamically. Meaning that every Apache process is allowed to spin up a PHP process. This means that Servebolt doesn’t limit your PHP workers at all.

Why PHP Worker limits are bad

To have the performance of your site be limited by PHP Workers is not ideal. When your traffic surges and start to run out of workers, the first thing to notice is that requests start queueing. This means your pages will be delivered with delayed responses. The first thing to notice when that happens is higher time to first byte (TTFB).

But it gets worse. If the queue continues to grow, caused by even more traffic, you’ll run into even more issues. Once traffic is just getting too high, that’s when you run into real problems. To the point where pages stop responding at all. Ultimately resulting your site to go down.

What are Servebolt’s limits?

Where our competitors are limiting their PHP workers – at best for their most expensive plans – to 16 PHP workers, we already provide more than that for our Pro plans which start at $70 a month currently. Having enough CPU should never be a bottleneck for a website or e-commerce store. That’s why we have the “Enough CPU” policy.

All our plans scale as you’d expect a scalable platform to do. Learn more about how to calculate how much traffic your site can handle.

But what about PHP memory limit & RAM?

Every single PHP process has access to the maximum amount available as set as PHP memory limit on your Bolt. And you can upgrade it to 1GB if necessary, but it rarely needed on our Bolts. This means you never run out of PHP worker limits, but you may be limited by PHP memory limits.

A common bottleneck when scaling a website is RAM. At Servebolt we provide Unlimited RAM for all price plans. This ensures that you don’t need to worry about having enough RAM. Servebolt take care of that. We make sure your site always has enough RAM available. Servebolt can scale your website more easily out of the box than most other hosting alternatives.

So when I said “It’s a little bit silly to be having the problem of exceeding PHP worker limits”, I meant it. We’re in the business of serving you the fastest, most scalable websites possible. It makes no sense whatsoever to limit you in any way while doing so.

If you’re looking for the fastest, most scalable hosting that doesn’t limit your CPU and RAM resources, do reach out to us and we would be happy to set up a copy of your site for testing purposes. You can also create an account directly and set up a copy of your site yourself.

Remkus de Vries

Head of Partner & Customer Relationships

Remkus is Head of Partner & Customer Relationships at Servebolt. He co-founded and lead WordCamp Europe and WordCamp Netherlands. During more than a dozen years he's spoken at many WordCamps and WordPress Meetup groups.

Related Posts