PostgreSQL / MySQL Connection Pool, RAM & Worker Concurrency Calculator
Every idle PostgreSQL backend process consumes ~8–12 MB RAM (more with work_mem under load); keeping direct database connections near (2 × CPU cores) + SSD spindles behind a pooler or capped PHP-FPM `pm.max_children` prevents memory exhaustion and lock contention.
Interactive Parameters & Live Verdict
Rule Diagnostics & Recommendations
Engineering Formula & Verification Notes
Reserves 50% of DB RAM for shared_buffers/InnoDB buffer pool and OS page cache, limiting per-connection memory + 1.5x work_mem overhead to 45% of DB RAM, while sizing optimal active pool concurrency around the classic HikariCP `(2 × cores) + effective_spindle` rule.
Worked Example: 4-vCPU, 8 GB VPS Running 60 PHP/Node Workers
An 8 GB DB server should dedicate ~4 GB to buffer cache and cap total connections well under ~108. However, throughput peaks around 12–20 concurrent active queries; placing a connection pooler in front of 60 app workers prevents CPU thrashing.
- Use `PDO::ATTR_PERSISTENT => false` unless you strictly cap `pm.max_children` below `max_connections`.
- Always monitor slow queries before raising `max_connections`.
Common Database Pool Sizing Mistakes
Raising `max_connections = 1000` fixes "too many connections" errors temporarily while setting up catastrophic OOM crashes.
- Setting `work_mem` to 128 MB with 200 connections (potential 25+ GB RAM burst).
- Leaving idle microservices holding open DB connections unnecessarily.
Database Server Sizing Quick Reference
| DB RAM / vCPU | Buffer Cache | Optimal Active Pool |
|---|---|---|
| 4 GB / 2 vCPU | 2.0 GB | 8–12 conns |
| 16 GB / 8 vCPU | 8.0 GB | 20–28 conns |
| 64 GB / 16 vCPU | 32.0 GB | 36–48 conns |
Frequently Asked Technical Questions
Why is a smaller database connection pool often faster?
Fewer concurrent queries reduce lock contention, cache-line bouncing, and CPU context switching on NVMe storage.
Should I use session or transaction pooling in PgBouncer?
Transaction pooling maximizes connection reuse for stateless web requests (avoiding session-level prepared statements unless configured).
How much RAM should MySQL InnoDB buffer pool get?
On a dedicated DB host, 60%–70% of RAM; on a shared app+DB VPS, keep it around 35%–50%.