Why it matters
Too many connections slow a database down; too few queue requests. Autoscaling app instances multiply the problem.
This keeps the total under the limit while covering your load.
How to use it
- Type or paste your input; the example shows the format.
- Press Calculate. Results also update as you type.
- Read the summary line, then the table, notes or output below it.
- Copy or download what you need. Nothing leaves this page.
FAQ
Why not just raise max_connections?
Each Postgres connection costs memory and context switching; more is often slower.
When do I need PgBouncer?
When instances × pool size exceeds what the database handles well.
Is my input uploaded?
No. The tool runs in your browser and nothing you type, paste or open is sent anywhere.
Can I rely on the result?
It follows the public specification or formula named on this page and says where it simplifies. Check anything critical against the official tool or documentation before you ship it.