Server Management: Dedicated PHP-FPM Pool per Project With Live Worker Counters
Every site on a managed server used to share one PHP-FPM pool, so a traffic flood on one site could exhaust the workers of every other site on the box. Each project can now run on a dedicated pool of its own.
01 One pool per project
Each project has a PHP-FPM Pool card in its details page. Enable it and the agent clones the server-wide pool configuration into a pool owned by that project, points the project's Apache vhost or vhosts at it in place, and reloads PHP-FPM and Apache gracefully. The vhosts are not regenerated, so your customisations stay exactly as they are. Every step is validated first and rolled back on failure.
02 Live counters and a pool editor
The card shows live counters and an editor for the pool file, so you can cap a site at, say, twelve workers while the rest of the server keeps its own limits.
| Counter | What it tells you |
|---|---|
active / idle / queued | Worker processes serving, waiting, and requests queued behind them |
max-children hits | How often the pool ran out of workers |
slow requests | Requests that exceeded the slow-request threshold |
03 Opt-in, and safer saves
The feature is strictly opt-in: projects you do not switch keep running on the shared pool, untouched. Separately, PHP-FPM configuration saves now wait for the reload to finish before the next change is accepted.