Monitoring PHP-FPM Worker Utilization

Busy and idle process counters help diagnose saturation and poor pool sizing.

What It Does and When to Use It

Set parameters in the FPM pool configuration; avoid exposing pool status publicly. The web server handles HTTP, the PHP worker executes scripts, and CLI has separate configuration and lifecycle.

Requirements, Inputs and Expected Behavior

Confirm the runtime, extension, environment variables, and permissions before running the examples in production. High busy workers alone do not identify whether CPU, locks or upstream services are the bottleneck.

Example 1: Basic Operation

Set parameters in the FPM pool configuration; avoid exposing pool status publicly.

pm.status_path = /fpm-status
pm.max_children = 12

Example 2: Behavior and Validation

Run the matching status or validation command on the intended host.

curl -s http://127.0.0.1/fpm-status?json

Practical Example: Application Use

Correlate capacity, worker crashes and slow requests using logs and process state.

sudo systemctl status php8.4-fpm --no-pager
sudo journalctl -u php8.4-fpm -n 35 --no-pager

Important Behavior and Edge Cases

The second example highlights: Run the matching status or validation command on the intended host. The practical example adds: Correlate capacity, worker crashes and slow requests using logs and process state.

Comparison with Related Approaches

Common Beginner Mistakes

Key Takeaways

• Busy and idle process counters help diagnose saturation and poor pool sizing.
• Correlate capacity, worker crashes and slow requests using logs and process state.
• Check the effective configuration in the SAPI serving requests before changing production.