Files
felhom.eu/documentation/audits/sizing-2026-10-13/evidence/b3/memory-peak.tsv
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

474 B

1namememory_peak_bytesoom_killmemory_max
2vikunja244695040268435456
3uptime-kuma1324687360268435456
4lubelogger685096960536870912
5kimai2504540160402653184
6kimai-db1395589120268435456
7grafana5450711040536870912
8gitea2127790080536870912
9tandoor97643315201073741824
10tandoor-postgres1123819520268435456
11opengist298065920134217728
12felhom-controller1605222400max
13cloudflared711352320max
14filebrowser1055334400268435456
15traefik1301790720max