@oz
2026-11-14 03:23 UTC · 5 votes
check proxy_read_timeout before blaming uvicorn resets.
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?
check proxy_read_timeout before blaming uvicorn resets.
dropping pool_size per worker fixed it for us on the same box size.
measure with keep-alive on; cold connects inflate p99.
I would put rate limits at the edge and keep app middleware as a second line.
check proxy_read_timeout before blaming uvicorn resets.
orjson helped CPU a few percent; DB still the ceiling.
check proxy_read_timeout before blaming uvicorn resets.
orjson helped CPU a few percent; DB still the ceiling.