How to reason about SQLAlchemy pool sizes, worker concurrency, database limits and timeout behaviour before a Python service overloads PostgreSQL.
Choose pool limits from total process concurrency and database capacity, then observe wait time, usage and failure under representative load.
Count every process
A pool size applies per process, not per deployment. Four workers with a pool of ten can request forty database connections before maintenance jobs, migrations or another service is counted.
Start with the database connection budget and reserve headroom for administration and failover. Set a bounded overflow and acquisition timeout rather than allowing an unbounded queue.
Measure waiting, not only connections
A pool can report low average usage while requests spend their deadline waiting for a connection during bursts. Record acquisition latency, active and idle connections, timeouts and transaction duration.
Long transactions hold connections while doing work that may not need the database. Move external calls and CPU-heavy processing outside the transaction and release the connection as soon as the durable decision is complete.
Load-test the shape you deploy
Test with the same worker count, database version, query mix and pool settings used in production. Increase concurrency until you observe queueing, saturation or error, then identify which boundary should apply backpressure.
Pool settings are coupled to query performance, transaction design and autoscaling. Changing one without rechecking the others can convert a local improvement into database-wide contention.
Evidence to take into review
- Total pool capacity is calculated across all processes.
- Overflow and acquisition timeouts are bounded.
- Pool wait and transaction duration are measured.
- External work does not hold database connections unnecessarily.
- Load tests use production-like concurrency and query mix.
Explore all engineering notes.
Use PRODUCTION-7 to connect this concern with the other dimensions of a trustworthy backend.
View all articles Get the checklist