KBY Engineering Utilities

Database Connection Pool Sizer

Calculate a per-pod connection-pool upper bound from database capacity, peak pod count, and an explicit operational reserve.

Accuracy contract: The floor division is exact for the supplied capacity and reserve, but real safety depends on accounting for every connection consumer and deployment overlap.

Inputs

Defined calculation contract

Database max_connectionsThe absolute maximum connections the database cluster or proxy can accept.Maximum podsThe highest number of application pods that the HPA will scale out to.Reserved connectionsConnections reserved for migrations, superusers, or other services.

Exact output

Calculation result

Max connections per pod

Max application pods

500

Database max_connections

480

Total available to pods

Reserved for operations

Unallocated connections

Recommendation

Use 9 connections per pod as an arithmetic upper bound under the supplied assumptions. At 50 pods this allocates 450 application connections and leaves 50 connections outside those pools.

Include every database consumer in the reserve: administrators, replication or monitoring, migrations, other services, pool maintenance connections, and temporary overlap during deployments. Validate the result with database and pool metrics before production use.

Versioned sources

PostgreSQL: max_connections

Deterministic v2026.08.1 — Advanced · 2 min