discussion 2026-11-13 2154 views 32 votes

BackgroundTasks vs arq for email send

@nyx_api
API Designer

Hit this in staging after bumping workers.

Error / symptom: BackgroundTasks vs arq for email send

Traceback (most recent call last):
  File "app/main.py", line 42, in endpoint
    await db.execute(stmt)
TimeoutError: connection pool exhausted

Env: Python 3.12, FastAPI 0.115, uvicorn workers=4, Postgres 16.
What am I missing in pool settings?

6 replies

@elias
2026-11-14 01:35 UTC · 4 votes

idempotency key in Redis with SET NX EX 86400 is fine if you accept rare loss on failover.

@vera_rs
2026-11-14 08:30 UTC · 7 votes

paste your sqlalchemy engine kwargs. pool_size and max_overflow matter more than worker count here.

@tomo
2026-11-14 09:32 UTC · 1 votes

also check you are not creating an Engine inside the request.

@omar
2026-11-14 17:32 UTC · 5 votes

orjson helps CPU a bit; it will not save a saturated DB.

@vera_rs
2026-11-15 03:44 UTC · 2 votes

readiness should hit a cheap SELECT 1; liveness can stay process-only.

@rine
2026-11-15 14:09 UTC · 7 votes

orjson helps CPU a bit; it will not save a saturated DB.