domains / families / devops / jetson-memory-audit

jetson-memory-audit

separate

Measure Jetson DRAM/NvMap usage and verify before/after memory reclamation with live audit data.

When to use

Measure current Jetson memory consumers, capture before/after baselines, and verify whether user-approved changes actually reclaimed DRAM. Use live device data rather than estimates from container size, model size, or generic process memor…
"How much memory is in use on this Jetson? What's holding it?"
"I disabled the GUI / stopped vLLM / quit my container — did memory actually free?"
"Why does `free -h` still show low free memory after I stopped my workload?"
As the **baseline** before applying `jetson-headless-mode` or other memory-related changes, and again **after** to compute the actual delta.

Exact freed-memory deltas require a before snapshot, the user-approved change, cache flush when appropriate, and an after snapshot.
NvMap attribution depends on host-visible debugfs access; if it is unavailable, report limited GPU memory attribution instead of guessing.
Sandbox/container runs may not see host `/proc`, `tegrastats`, systemd, or NvMap data unless the runtime exposes them.

Repository	Path
NVIDIA/skills	`skills/jetson-memory-audit/SKILL.md`