PHP Workers: Your Site's Hidden Limit

Most people pick hosting by disk space and bandwidth, then wonder why the site chokes at peak even with plenty of free space. The culprit is often an invisible parameter: the number of PHP workers. That is how many requests your site can process at the same moment. If there are too few, visitors wait in a queue.

What a PHP worker actually is

Picture the checkout lanes in a shop. Each worker is one lane. When a visitor requests a page that is not served from cache (say a cart, login, or payment), it occupies one lane until the page is assembled. If you have 2 lanes and 5 shoppers with dynamic requests arrive at once, three wait. The longer a page takes to generate, the longer the lane stays busy.

Why caching solves most of the problem

Good news: static pages served from cache or a CDN use almost no worker at all. That is why a blog or brochure site handles thousands of visits a day on just 2 workers. The problem appears on dynamic sites — WooCommerce, memberships, forums — where every action is generated fresh. There the worker count directly decides how many shoppers you can serve simultaneously.

Signs your workers are not enough

A few symptoms are easy to spot: the site is fast when empty but slow exactly when traffic peaks; occasional 502 or 504 errors appear; your hosting stats show the queue is full. If this happens right during a campaign or sale, you lose sales at the worst possible moment.

More workers or a faster site?

There are two paths. The first is buying more workers — like adding lanes. The second, often smarter, is speeding up page generation so each lane turns shoppers around faster. If you cut generation time from 800 ms to 300 ms, the same worker count serves nearly three times as many people. Object cache (Redis), a newer PHP version, dropping surplus plugins, and database optimization all help here.

How many workers is enough

A rough guide: a small dynamic site with a few concurrent shoppers — 2 to 4 workers. A serious store with steady traffic — 4 to 8 and up. But the number alone means nothing without page speed; slow generation eats even a large worker count. So look at both together.

Our plans combine enough PHP workers with NVMe disks and caching, so the site survives peaks without choking. Compare the plans or see WordPress hosting for stores.