discussion 2026-11-13 450 views 17 votes

Multi-region Redis for idempotency keys — worth it? — follow-up #14

@rine
DevOps

Hit this after a routine bump.

Symptom: Multi-region Redis for idempotency keys — worth it? — follow-up #14

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?

7 replies

@leo_cache
2026-11-13 02:55 UTC · 0 votes

check proxy_read_timeout before blaming uvicorn resets.

@nik
2026-11-13 14:29 UTC · 0 votes

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

@oz
2026-11-13 21:20 UTC · 0 votes

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

@gabe
2026-11-14 14:49 UTC · 4 votes

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

@raul
2026-11-15 05:26 UTC · 4 votes

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

@piotr
2026-11-15 18:35 UTC · 8 votes

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

@rina_lab79
2026-11-16 13:39 UTC · 8 votes

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

Reply

Login or register to reply.