fix(api): increase memory/workers for 500-device scale, add blog post

API container was OOM-killed under 500-device mock load due to debug
logging, single worker, and 512MB limit. Bumped to info logging,
2 workers, and 1GB. New blog post documents the incident.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jason Staack
2026-03-21 07:33:35 -05:00
parent 4092806fbc
commit c9ca0d376c
3 changed files with 285 additions and 3 deletions

View File

@@ -13,9 +13,9 @@ services:
env_file: .env
environment:
ENVIRONMENT: dev
LOG_LEVEL: debug
LOG_LEVEL: info
DEBUG: "true"
GUNICORN_WORKERS: "1"
GUNICORN_WORKERS: "2"
DATABASE_URL: postgresql+asyncpg://postgres:postgres@postgres:5432/tod
SYNC_DATABASE_URL: postgresql+psycopg2://postgres:postgres@postgres:5432/tod
APP_USER_DATABASE_URL: postgresql+asyncpg://app_user:app_password@postgres:5432/tod
@@ -62,7 +62,7 @@ services:
deploy:
resources:
limits:
memory: 512M
memory: 1G
networks:
- tod
- tod_remote_worker