felhom.eu/documentation/audits/sizing-2026-10-13/evidence/romm/memory-peak.tsv at ade357a14ea3dd69ed2bf55e58eefe2f0d965eff - felhom.eu - Gitea: Git with a cup of tea

admin/felhom.eu

0 Fork 0

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

10 lines

281 B

Plaintext

Raw Blame History

 name	memory_peak_bytes	oom_kill	memory_max
 romm	769310720	0	805306368
 romm-db	151363584	0	402653184
 romm-redis	38924288	0	134217728
 opengist	29663232	0	134217728
 felhom-controller	160522240	0	max
 cloudflared	71135232	0	max
 filebrowser	105533440	0	268435456
 traefik	129253376	0	max