Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

WordPress

PHP worker sizing: match concurrency to memory, CPU and request time

Published August 2026 · 2 min read · Updated 2026-09-05

PHP worker sizing decides how many PHP requests can execute concurrently and how much memory that concurrency can consume. Too few workers create queues; too many can exhaust RAM or overload the database. The right number comes from request duration, traffic concurrency, per-worker memory, and the rest of the stack.

Measure real concurrent PHP demand

Separate cached/static requests from requests that actually reach PHP. During a busy period, record active/idle workers, queued requests, request duration, CPU usage, and memory. A site serving 100 requests per second from cache may need fewer PHP workers than a lower-traffic uncached WooCommerce site.

Look for pool saturation messages or queue growth before assuming every slow page is a worker problem.

Budget memory per process

Measure representative PHP process RSS across normal and expensive requests, then reserve RAM for the operating system, web server, database, cache, mail/control-panel services, and filesystem cache. Multiplying a maximum worker count by a guessed memory_limit can overstate or understate real pressure.

Watch OOM events and swap activity during bursts.

Reduce slow request occupancy

A slow database query, remote API call, image task, or plugin lock can hold a worker for seconds. Fixing that latency can increase throughput without raising the worker ceiling.

Profile expensive endpoints and move long background work out of synchronous web requests where the application supports it.

Increase gradually and retest

Raise the pool limit in controlled steps only when CPU, RAM, and database capacity have headroom. Repeat the same traffic or load scenario and verify queue time improves without memory pressure or database contention.

  • Count uncached PHP concurrency.
  • Measure worker memory.
  • Fix long-running requests.
  • Retest after each pool change.

Next step

Size PHP workers from real concurrent uncached requests, per-process memory and database capacity, then retest before raising the pool again.

Explore DotMoose WordPress hosting

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move