jtop-pss debuts, terminal monitor tracks PSS, USS, and CPU timing

If top and htop leave you guessing about where a process’s RAM really went, jtop-pss made a direct pitch: stop staring at RSS alone and look at PSS, USS, and CPU timing that is precise enough to catch short bursts. The first beta arrived as a terminal process monitor built around accurate memory accounting, and the point of it was practical, not decorative. When a service looks bloated, the difference between shared pages, private pages, and what would actually be freed on exit is the difference between a useful diagnosis and a noisy guess.

The author framed the project as a first step in public, too. jtop-pss was the author’s first thing on GitHub, which made the launch note feel less like a polished product drop and more like a developer asking a blunt question: would other Rust users actually use this? That matters here because the tool is not trying to invent a new category. It is stepping into a small but real space of Linux monitors that try to answer memory questions more honestly than the default process table.

That honesty starts with the metrics. RSS is convenient, but it can overcount shared libraries and other shared pages, which makes it a poor stand-in for true per-process RAM use. PSS, by dividing shared memory proportionally across processes, and USS, by showing the memory that would be freed if the process died, tell a cleaner story. Linux already exposes the data needed for that through /proc/PID/smaps_rollup, the aggregate roll-up of the same mapping statistics that the kernel added to make memory sampling faster for large processes.

jtop-pss also lands alongside existing Rust tooling rather than ahead of a vacuum. rupss, another Rust terminal UI for Linux memory monitoring, already reports RSS, USS, PSS, swap, and CPU% derived from tick deltas between samples. That makes jtop-pss part of a focused niche of terminal monitors aimed at helping developers understand memory pressure, not just admire a live dashboard.

The launch showed only modest early visibility, with the forum topic sitting at 0 replies in the crawl that captured it. That fits the shape of the announcement: a beta, a first GitHub project, and a narrow but real promise. For anyone trying to decide whether to open jtop-pss instead of the usual top-style tools, the answer is simple: use it when shared memory is muddying the picture and you need to know what a process actually owns.