felhom.eu/documentation/audits/sizing-2026-10-13/evidence/romm/memory-peak.tsv at ed59bf3cbdd9f9fb4b051ea87dac2f621005a975

Files

T

admin c885b5acf4 Audit: what a Felhom box needs — floor, 64 apps' memory and CPU, power (N100 bench); R-993..R-995; R-231 due check read green

Measured on demo-felhom (N100, 16 GB): 61 apps deployed and removed through the
product, sampled every 5 s; heavy apps with one real action (Immich 200 photos,
Jellyfin transcode, Paperless OCR, Nextcloud 500 MB, ...). sizing.json for the
estimator (tools/build_sizing.py), SIZING.md with the proposed minimum machine,
METHOD.md. Power is RAPL CPU-package only (no meter). R-993 asks the operator to
approve the minimum machine; R-994 lists catalog limits/requests that are too low;
R-995 records leftover unnamed volumes after removal. R-231's dated check measured:
dooplex-backup.service success, journal green.

2026-10-13 13:23:51 +02:00

281 B

Raw Blame History

1	name	memory_peak_bytes	memory_max
2	romm	769310720	805306368
3	romm-db	151363584	402653184
4	romm-redis	38924288	134217728
5	opengist	29663232	134217728
6	felhom-controller	160522240	max
7	cloudflared	71135232	max
8	filebrowser	105533440	268435456
9	traefik	129253376	max

281 B Raw Blame History

281 B

Raw Blame History