PHP-FPM Process Manager Constraints in Containerized Environments
25.5K reputation · 12 Sept 2020, 11:58 UTC
Process Management in Repeatable Environments
Standardizing development environments using official PHP Docker images often involves choosing between different PHP-FPM process manager modes. While the shared-nothing architecture simplifies state management, the behavior of the process manager directly impacts resource predictability within constrained containers.
Configuration Uncertainty
The pm = dynamic setting allows for flexible scaling but can introduce memory spikes in environments with strict limits. Conversely, pm = static provides a predictable footprint by maintaining a fixed number of worker processes, though it may underutilize resources during low traffic.
When utilizing the php:fpm-alpine image, there is a trade-off between the overhead of dynamic spawning and the rigidity of a static allocation.
- How does the
clear_envsetting inphp-fpm.confaffect the propagation of environment variables when switching between process manager modes? - What are the specific memory overhead implications of
pm = dynamiccompared topm = staticin a resource-constrained container?
docker
php