RAM Tracker

A project by Qalarc — AI systems studio, Sydney, Australia. Built, shipped and maintained by Qalarc.

GTK4 memory monitor that tells the truth about Linux RAM — zram-compressed accounting, AMD GTT, per-process PSS from smaps_rollup, and glibc malloc_trim — instead of the usual RSS theatre.

Python 3GTK4 / PyGObjectpsutilSQLiteprocfs/sysfs parsing

Most memory monitors lie by omission: they show RSS, which double-counts shared pages and ignores compression, then panic the user about 'free' memory that the kernel is using perfectly well as cache. RAM Tracker was built on a 124 GB zram machine to show what is actually happening: the full /proc/meminfo breakdown, swap that is really a compressed RAM disk (with compression ratios from the kernel's own mm_stat), and AMD iGPU GTT allocations pulled from sysfs.

Per-process views use PSS from smaps_rollup — proportional set size that fairly splits shared libraries — and the process list includes an agent-awareness layer: a token/cost tab reads the local AI coding tooling's SQLite database to show what your AI assistants are actually costing you per session.

It also feeds gmux: a live agent-feed JSON endpoint lets the terminal multiplexer display memory pressure alongside each agent pane.

Capabilities

Full /proc/meminfo breakdown with plain-English interpretation
Zram-aware swap accounting with live compression ratios from mm_stat
AMD GPU GTT memory from amdgpu sysfs
Per-process PSS via smaps_rollup (fair shared-memory accounting)
glibc malloc_trim invocation for heap release
AI-agent cost tab reading opencode session data
JSON agent feed consumed by gmux terminal panes

RAM Tracker

Capabilities

Tags