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

16 lines
474 B
Plaintext

name memory_peak_bytes oom_kill memory_max
vikunja 24469504 0 268435456
uptime-kuma 132468736 0 268435456
lubelogger 68509696 0 536870912
kimai 250454016 0 402653184
kimai-db 139558912 0 268435456
grafana 545071104 0 536870912
gitea 212779008 0 536870912
tandoor 976433152 0 1073741824
tandoor-postgres 112381952 0 268435456
opengist 29806592 0 134217728
felhom-controller 160522240 0 max
cloudflared 71135232 0 max
filebrowser 105533440 0 268435456
traefik 130179072 0 max