admin/app-catalog-felhom.eu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

romm: two web workers, not four - the actual cause (R-635)
gates / gates (push) Successful in 1s
Details

Browse Source 
WEB_SERVER_CONCURRENCY=2, limit left at 768M. No image: line moved.

768M was still a guess and it was wrong: kills slowed from ~12/min to ~7/min and stopped nothing.
Measured instead - each warm uvicorn worker holds ~216 MiB, so four plus the master reach ~882 MiB,
and the cgroup's memory.peak read exactly 768 MiB.

/init:143 runs --workers "${WEB_SERVER_CONCURRENCY:-4}". Four is a server default; this is one
household on one small box. Two measure ~450 MiB, fit 768M with headroom, and halve the CPU churn.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
authentik Default Admin
2026-09-22 17:55:01 +02:00
parent 886956dcc7
commit f4eb94f195
2 changed files with 36 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+29
View File
@@ -1,3 +1,32 @@
## romm runs TWO web workers, not four — the actual cause (2026-09-22, R-635)
`WEB_SERVER_CONCURRENCY=2`, with the limit left at the 768M of the previous entry. **No `image:`
line moved.**
**768M was still a guess, and the guess was wrong** — it slowed the kills from ~12/min to ~7/min and
stopped nothing. The number came from measuring instead:
```
pid 2318697 RSS 216 MiB <- warm uvicorn worker
pid 2318717 RSS 215 MiB <- warm uvicorn worker
pid 2319627 RSS 63 MiB <- just restarted after a kill
pid 2319629 RSS 62 MiB <- just restarted after a kill
pid 2315417 RSS 18 MiB <- gunicorn master
```
Four warm workers plus the master reach **~882 MiB** before nginx and the job runner in the same
container, and the cgroup's own `memory.peak` read **exactly 768 MiB** — it hit the new ceiling and
was killed there.
**The lever was in the image all along:** `/init:143` runs
`--workers "${WEB_SERVER_CONCURRENCY:-4}"`. **Four workers is a server default on an appliance
serving one household.** Two measure ~450 MiB and fit 768M with headroom, and they halve the CPU
churn as well — the host's load average had been sitting at **5.2 while otherwise idle**.
**The lesson is not about romm.** A version move is not only an `image:` line: the new version's
*shape* — worker counts, per-worker footprint — has to be measured too, and a walk that lasts
minutes cannot see a ceiling that is reached in two hours.
## romm gets 768M — 5.3.0 does not fit in 512M (2026-09-22, R-635)
**No `image:` line moved, so no `catalog_since` moved.** `romm` 512M -> **768M**; the header and