ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
WordPress relies on the wpdb class to open a MySQL connection for each request. By default it does not maintain an application‑level pool, but persistent connections can be enabled via mysqli.allow_persistent . When PHP‑FPM spawns more child processes than the database permits, the server can emit "Too many connections" errors during traffic spikes. The core
The goal is to decide whether enabling the DoctrineBundle persistent option (which sets PDO::ATTR_PERSISTENT ) is advisable when running Symfony under PHP‑FPM, weighing the benefit of reduced connection churn against the risk of exhausting the database’s max_connections due to each PHP‑FPM worker maintaining its own persistent connection. Constraints include
PHP‑FPM’s fixed worker pool causes request queuing when concurrent requests exceed available workers, and the pm.max_requests limit triggers worker termination pauses that manifest as latency spikes under load. The appropriate configuration of pm.max_children remains unclear for workloads with variable concurrency, while the default file‑based session lockin
Zend\Db\Adapter\Adapter establishes a physical database connection lazily, only on first query execution or an explicit getDriver()->getConnection() call. This defers connection overhead for requests that do not need database access. Zend\Db does not implement its own connection pool. Pooling behavior depends on the PDO driver, the database server, and PH
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 contai
Clarify the documented connection management behavior of Doctrine DBAL and ORM in a typical PHP request lifecycle and the operational limits that apply to connection reuse. Doctrine DBAL does not implement an application-level connection pool. A DBAL Connection wraps a single PDO instance per request and the ORM typically uses one EntityManager per request.
Goal: Determine the appropriate PHP-FPM pm.max_children value that prevents intermittent MySQL 'Too many connections' errors when MODX Revolution's xPDO persistent_connection system setting is enabled. Constraints/uncertainty: xPDO reuses a single PDO instance per request but does not share persistent connections across separate PHP-FPM workers; idle persist
wordpress
symfony
zend
docker