Skip to content

v1.1.14 — Accurate per-site RAM tracking

Choose a tag to compare

View all tags
@ethandacat ethandacat released this 14 May 05:11
· 2 commits to main since this release
v1.1.14
3054bee

Fix: per-site RAM now always reads from cgroup

Previously, RAM tracking for hosted sites only worked for processes that were started in the current panel session. Any site that was already running when the panel restarted (recovered processes) would show 0 MB in the dashboard.

What changed

  • sampleProcs() now queries the DB for all running sites instead of only the process Map
  • Reads cgroup/memory.current directly for each — the same kernel-level source used for memory limits
  • Counts all forked workers (gunicorn, node cluster, PHP-FPM, etc.), not just the parent PID
  • The pidRss() fallback and the requirement for a tracked PID are gone entirely
Assets 2
Loading