Observed Signal · Apr 11, 2026 · Technical Release · Source: DEV Community · Impact: 1/5 · Sentiment: Neutral
Tuning PHP-FPM for Laravel Performance
This technical guide explains how to tune PHP-FPM for Laravel applications, covering process manager modes (static, dynamic, ondemand), how PHP-FPM worker processes handle requests, and the key settings that determine throughput and stability. It provides a formula for calculating pm.max_children from available RAM and average worker memory, guidance on PHP memory_limit, pm.max_requests for process recycling, request timeouts, and slow-log configuration for diagnosing slow requests. The article includes recommended example configurations for 1GB, 2GB, 4GB and 8GB servers (Deploynix-managed), monitoring tips using the PHP-FPM status page and Deploynix integration, and validation/restart/test commands (php-fpm8.4 -t, systemctl restart, wrk/ab). Practical recommendations emphasize measuring real worker memory, leaving headroom, and iterating based on observability metrics.
Operational server tuning guidance is useful for web performance but is a narrowly scoped engineering how-to with limited direct impact on the broader AdTech/MarTech industry.
Track DigitalOcean Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- PHP-FPM manages a master process and a pool of worker processes; each worker handles one request at a time.
- PHP-FPM supports three pm modes: static, dynamic, and ondemand, each with different trade-offs for memory and latency.
- The recommended formula: max_children = (Total Available RAM - RAM used by other services) / Average RAM per PHP worker.
- Typical Laravel worker memory ranges: simple CRUD 30–40 MB, medium 40–60 MB, complex requests 60–120+ MB.
- Provides tuned example pool configurations and recommendations for 1GB, 2GB, 4GB, and 8GB Deploynix-managed servers.
Connected Companies & Entities
1 Entity mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
PHP-FPM Tuning: 5 Settings That Decide p99
A technical guide explains five php-fpm configuration settings that heavily influence p99 latency for PHP web apps: pm.max_children, pm.max_requests, request_terminate_timeout, pm.process_idle_timeout (ondemand only), and listen.backlog. The author explains how to calculate pm.max_children from available RAM and average worker RSS, why pm.max_requests protects against memory growth, why request_terminate_timeout is the reliable kill switch, when ondemand is appropriate, and how listen.backlog interacts with the kernel (net.core.somaxconn) during bursts. A real-world c5.large Laravel 12 tuning example shows p99 improving from ~4800ms to ~380ms after switching to static pools, lowering max_children and increasing backlog and recycle settings. The article also summarizes when to consider Laravel Octane as an architectural alternative after tuning.
Laravel Queue Stopped — Root Cause Was PHP-FPM
A developer debugging a Laravel application on a cPanel server discovered that recurring queue stoppages and Make.com request timeouts were caused by infrastructure issues rather than the queue itself. The queue worker had been started with nohup and disappeared after server restarts; moving execution to a cPanel Cron job with /bin/flock and --stop-when-empty made the worker lifecycle more resilient. Separately, slow or queued HTTP requests were traced to an overly conservative PHP-FPM configuration (pm.max_children = 5, pm.max_requests = 20, pm.process_idle_timeout = 10) on a 65 GB / 20-core server. The author recommends tuning PHP-FPM to match server capacity and diagnosing each layer independently.
Laravel API Architecture Guide for Morocco (2026)
A practical 2026 guide to building production-grade APIs with Laravel, aimed at Moroccan freelancers and teams. The author asserts Laravel remains the top PHP framework for APIs and draws on 40+ shipped projects to recommend specific tools and patterns: Eloquent ORM, Sanctum for auth, Scout for full-text search, Queues with Horizon, Octane (Swoole/RoadRunner) for performance, and ecosystem tools like Telescope and Vapor. The guide outlines a standard project structure, best practices (URL versioning, FormRequests, API Resources, services/DTOs), security and rate-limiting advice, authentication flows for SPAs and mobile, deployment options (Forge with DigitalOcean/Hetzner, Vapor on AWS, Cloudways, Coolify), and typical Moroccan project budgets and timelines. FAQs cover PHP version (8.3+), API documentation tools (Scribe/Scramble), and timezone/work practices for Morocco (GMT+1).
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.