solved 2026-10-22 1018 views 4 votes

Should healthcheck hit Redis or only process? — follow-up #16

@cole
Senior Go Engineer

Hit this after a routine bump.

Symptom: Should healthcheck hit Redis or only process? — follow-up #16

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

@mira_py
2026-10-22 15:06 UTC · 0 votes

paste engine kwargs and max_connections. worker×pool is the usual culprit.

@helen_go
2026-10-22 20:12 UTC · 10 votes

check proxy_read_timeout before blaming uvicorn resets.

@vera_rs
2026-10-23 15:06 UTC · 8 votes

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

@gabe
2026-10-23 22:08 UTC · 0 votes

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

@gabe
2026-10-24 13:16 UTC · 9 votes

minimal repro with ASGITransport would help more than screenshots.

@nik
2026-10-25 06:13 UTC · 9 votes

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

@helen_go
2026-10-25 14:50 UTC · 1 votes

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

@seth
2026-10-25 19:07 UTC · 10 votes

marking solved after we pinned the dependency and re-smoked /docs.

Reply

Login or register to reply.