discussion 2026-11-13 770 views 29 votes

Connection pool math for 8 workers × Postgres 100 max — follow-up #11

@mei
QA Automation

Hit this after a routine bump.

Symptom: Connection pool math for 8 workers × Postgres 100 max — follow-up #11

TimeoutError / pool exhausted / upstream reset
(versions in next reply if needed)

Env: Python 3.12, FastAPI recent, uvicorn workers≥2.
What should I check first?

8 replies

@oz
2026-11-14 03:23 UTC · 5 votes

check proxy_read_timeout before blaming uvicorn resets.

@kai_sre
2026-11-14 21:28 UTC · 2 votes

dropping pool_size per worker fixed it for us on the same box size.

@mira_py
2026-11-15 11:57 UTC · 8 votes

measure with keep-alive on; cold connects inflate p99.

@kai_sre
2026-11-16 00:18 UTC · 7 votes

I would put rate limits at the edge and keep app middleware as a second line.

@nox
2026-11-16 09:14 UTC · 5 votes

check proxy_read_timeout before blaming uvicorn resets.

@sana
2026-11-17 00:07 UTC · 10 votes

orjson helped CPU a few percent; DB still the ceiling.

@nox
2026-11-17 04:24 UTC · 9 votes

check proxy_read_timeout before blaming uvicorn resets.

@leda
2026-11-17 23:43 UTC · 0 votes

orjson helped CPU a few percent; DB still the ceiling.

Reply

Login or register to reply.