Speed & performance · Explainer
How Many PHP Workers Does a WordPress Site Need?
Short answer
Most cached blogs need 2 to 4 PHP workers, small WooCommerce stores need 4 to 6, and busy stores, membership sites, and course sites need 6 or more. The exact number depends on how many uncached requests arrive at the same time and how long each one takes. Work it out with the formula in this guide, then check your host dashboard for how often you hit the limit.
Key takeaways
- A PHP worker handles one uncached request at a time, so your worker count is your limit for simultaneous dynamic requests.
- Cached pages do not use a PHP worker, so a high cache hit rate lowers the number of workers you need.
- Workers needed equal uncached requests per second multiplied by the average seconds each request takes.
- On Kinsta, a 1 GB memory pool gives 4 threads at 256 MB each or 8 threads at 128 MB each.
- WooCommerce sites should keep at least 128 MB of memory per PHP thread, according to Kinsta.
- When all workers are busy, new requests queue, and WP Engine reports 502 and 504 errors when the queue fills.
How many PHP workers does a WordPress site need?
Most cached blogs need 2 to 4 PHP workers, small WooCommerce stores need 4 to 6, and busy stores and membership sites need 6 or more.
No single number fits every site, because workers limit simultaneous work, not total visits. A blog with 10,000 visits a day can run on 2 workers if most pages come from cache, while a store with 500 visits a day can stall on 2 workers if many shoppers check out at once.
Kinsta documents the same split in its plan patterns: entry-level sites get 2 to 4 threads at 256 MB per thread, mid-tier sites get 6 to 8 threads, and upper-tier sites get 10 to 16 threads at 512 MB per thread.
What is a PHP worker?
A PHP worker is a PHP process that handles one uncached request at a time.
Kinsta calls the same thing a PHP thread. Each thread is a PHP process that handles one incoming request at a time, so more threads allow for more simultaneous requests. PHP.net describes the setting behind it, pm.max_children, as the limit on the number of simultaneous requests that will be served.
When a worker finishes a request, it becomes free for the next one in the queue. Kinsta notes that a thread idle for 10 continuous seconds ends, then is recreated at once when it is needed again.
How do you work out your number with a simple formula?
Multiply your peak uncached requests per second by the average seconds each uncached request takes.
That product is the number of workers busy at an average moment during your peak. If 5 uncached requests arrive each second and each takes 0.4 seconds, you need 5 times 0.4, which is 2 workers. If 10 arrive each second and each takes 0.5 seconds, you need 5 workers.
Work through these steps to apply it to your site:
- Find your busiest hour in your host or analytics dashboard, not your daily average.
- Count only uncached requests in that hour, such as checkouts, logins, cart updates, and search.
- Divide that count by 3,600 to get uncached requests per second.
- Multiply by your average PHP time per request in seconds.
- Round up, then add headroom for short bursts, because traffic arrives in clumps.
WP Engine makes the same point in its performance insights guide: page requests during the busiest hour show the maximum load your site received. For help reading those limits, see how to read a hosting plan's CPU and RAM limits.
How many workers do different types of sites need?
Start with the band for your site type, then adjust it with the formula and your limit chart.
| Site type | Starting point | Why it sits there |
|---|---|---|
| Brochure site or cached blog | 2 workers | Most pages come from cache and need no worker |
| Active blog with comments and search | 2 to 4 workers | Some requests bypass cache, but peaks are short |
| Small WooCommerce store | 4 to 6 workers | Cart, checkout, and account pages cannot use page cache |
| Growing store or sale event | 6 to 10 workers | Several shoppers check out at the same time |
| Membership or course site | 6 to 12 workers | Logged-in pages bypass cache for every member |
These bands match the Kinsta allocation patterns above, where entry-level plans sit at 2 to 4 threads and mid-tier plans sit at 6 to 8 threads. They are starting points, not a promise: a slow plugin or a long database query keeps each worker busy longer, so it raises the count you need.
A store also needs more memory per worker than a blog. WooCommerce recommends a WordPress memory limit of 256 MB or greater, PHP 8.3 or greater, and WordPress 6.9 or greater, as of November 2026. Kinsta adds that WooCommerce sites should keep at least 128 MB of memory per thread.
Why does caching change the number you need?
Caching changes the number because cached pages never reach a PHP worker.
Kinsta states that cached content bypasses PHP threads, which are only needed for database queries or data changes. WP Engine states the same point: many page requests are served from cache and therefore are not handled by a PHP worker.
The requests that still need a worker are the ones that differ per visitor. That list includes logged-in pages, cart and checkout pages, account pages, search results, form submissions, and admin-ajax.php calls.
If most of your traffic is logged in, caching helps far less, so your worker count matters far more. To cut worker use before you pay for more, raise your cache hit rate first. For the steps, read how to speed up WordPress.
How much memory does each worker need?
Each worker needs enough memory to finish one request without hitting the PHP memory limit.
Kinsta sets a default PHP memory limit of 256 MB per thread. Its pool tables show the trade-off: a 1 GB total memory pool gives 4 threads at 256 MB each or 8 threads at 128 MB each.
A 2 GB pool gives 4 threads at 512 MB each, 8 threads at 256 MB each, or 16 threads at 128 MB each. More threads with the same pool means less memory per thread. The maximum memory limit per thread is 1024 MB.
| Total memory pool | Threads at 256 MB each | Threads at 512 MB each |
|---|---|---|
| 1 GB | 4 | 2 |
| 1.5 GB | 6 | 3 |
| 2 GB | 8 | 4 |
| 4 GB | 16 | 8 |
Do not split a small pool into many thin threads for a store. Kinsta warns that WooCommerce needs at least 128 MB per thread, so a 1 GB pool split into 16 threads at 64 MB each falls below that floor. Check the hosting resources WooCommerce needs first.
What happens when you run out of workers?
New requests wait in a queue, and if the queue fills, visitors see errors.
WP Engine explains that when PHP workers cannot finish requests as fast as they arrive, a backlog forms. When all workers and the backlog are full, older requests are evicted and return a 504 error. A request that takes too long is killed to free its worker, which returns a 502 error.
WP Engine puts that 502 limit at 60 seconds: a request that takes longer than 60 seconds is rejected. Its queue also sorts traffic by type, with real human traffic in the highest priority queue and AJAX, XMLRPC, and well-known bot requests in a low priority queue.
That sorting got stricter in November 2026. WP Engine states that automated traffic can never use more than 80% of the available PHP workers. With 10 workers, bots can occupy 8 at most and at least 2 stay free for people.
If your site slows only during a crawl, the worker count may be fine and the bot traffic may be the cause.
How do you check if you have enough workers now?
Check how often your site hits its worker limit in the last 24 hours.
On Kinsta, open Sites, then your site name, then Info, to see the PHP thread limit reached count for the last 24 hours. Kinsta states that frequent hits may mean visitors face slow loads or trouble reaching the site. It also notes that one hit can cover a whole hour of full use.
Use these three checks together:
- Thread limit reached in the last 24 hours, in your host dashboard.
- Average PHP and MySQL response time, in the same performance view.
- Cache hit ratio, because a low ratio sends more requests to workers.
On WP Engine, open the performance insights page and look at page requests during the busiest hour and the cache hit ratio. A high busiest-hour count with a low cache hit ratio points to worker pressure. If the numbers are unclear, compare them with what PHP workers are before you change a plan.
How do you get more workers?
You either raise the memory pool on managed hosting or raise pm.max_children on a server you control.
On Kinsta, go to Sites, then your site name, then Info, then PHP performance, then Change. The PHP performance add-on costs $10 per additional 500 MB per month, as of November 2026. Kinsta gives this example: raising a pool from 1.5 GB to 3 GB costs $30 per month.
The add-on is prorated, so you can raise it for a sale and lower it after.
Kinsta also sets plan caps on the pool. Standard plans with a default pool of 4 GB or more cannot be increased further. Custom plans with a default pool up to 2 GB can rise to 4 GB, and custom plans above 2 GB can rise to 8 GB.
A standard staging environment is limited to 2 threads.
On WP Engine, the documented route is to move to a larger server with more PHP workers once the site cannot be optimised further.
On a VPS or dedicated server, PHP.net states that pm.max_children is mandatory and sets the limit on simultaneous requests. Raising that number only helps if the server has spare CPU and RAM.
Does a newer PHP version change how many workers you need?
A newer PHP version can shorten each request, which lowers the workers busy at any moment.
Kinsta lists PHP version among the factors that affect thread performance. It notes that newer versions can bring performance gains, bug fixes, and security updates. Shorter requests free workers sooner, so the same worker count handles more uncached requests per second.
Keep the version current for the same reason. Make WordPress Hosting states that for a new WordPress 7.1 install, the recommended PHP versions are 8.4.x and 8.5.x, while the absolute minimum is PHP 7.4. It also notes that PHP 8.2 reaches end of life on 31 December 2026.
For the version to pick, see which PHP version to use for WordPress.
What mistakes should you avoid?
Avoid sizing from monthly visits, because workers limit simultaneous requests, not monthly totals.
A second mistake is splitting a small memory pool into too many threads. More threads look like more capacity, but each thread gets less memory, and a request that runs out of memory fails with a 500 error. Keep WooCommerce at 128 MB per thread or more.
A third mistake is adding workers before fixing slow requests. A plugin that fires many admin-ajax.php calls can hold workers for seconds at a time. WP Engine lists view counters, popup plugins, and ad plugins that hit admin-ajax.php as types that overwhelm PHP workers.
A fourth mistake is judging the number from a quiet day. Size from your busiest hour and your next sale or launch, not from a normal Tuesday.
If your host allows a prorated pool increase, raise it before the spike, then lower it after. When the count still hits its limit at every peak, move up a plan, as described in when to upgrade from shared hosting.
Frequently asked questions
Is 2 PHP workers enough for a WordPress blog?
Yes, for most cached blogs. If most pages are served from cache, only a few requests reach PHP at the same time, so 2 workers can handle normal traffic. You need more when many visitors are logged in, comment, search, or submit forms at once, or when the thread limit chart shows frequent hits in the last 24 hours.
How many PHP workers does a WooCommerce store need?
A small store usually needs 4 to 6 workers, and a growing store needs 6 to 10, because cart, checkout, and account pages cannot use page cache. Keep at least 128 MB of memory per thread for WooCommerce. Size from your busiest hour with the formula in this guide, and watch for 502 or 504 errors during sales.
Do PHP workers affect SEO?
They affect it indirectly. Too few workers cause slow pages, queues, and 502 or 504 errors during peaks, and those hurt visitors and crawling. Enough workers keep uncached pages fast during busy hours. Caching, a current PHP version, and fixing slow plugins matter as much as the worker count itself.
Can I increase PHP workers without changing hosting plans?
It depends on your host. On Kinsta you can buy a PHP performance add-on at 10 dollars per extra 500 MB of memory pool per month, within the plan caps. On a VPS or dedicated server you can raise pm.max_children yourself if the server has spare CPU and RAM. On some managed hosts you must move to a larger plan.
Why does my site slow down when bots crawl it?
Bots request many uncached pages, and each one needs a PHP worker until it finishes. When workers fill up, real visitors queue behind them. WP Engine now caps automated traffic at 80 percent of workers so at least some stay free for people, and it puts bots in a low priority queue. Raising cache coverage and slowing crawl-heavy bots helps more than adding workers alone.
Sources
- PHP Performance Kinsta Docs
- PHP threads vs PHP memory limit Kinsta
- Manage PHP Workers and Prioritization WP Engine Support
- Letting humans skip the line: Why we capped PHP workers for automated traffic WP Engine
- FPM Configuration PHP.net
- WooCommerce Server Recommendations WooCommerce
- WordPress 7.1 Server Compatibility Make WordPress Hosting
- View Performance Insights WP Engine Support
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
