veloxquant_mlx.ui.memory module¶
Measured memory reporting for the control panel.
#27 forbids claiming memory savings the backend cannot prove. It does not require staying silent about memory — and showing genuinely measured numbers next to the accounting-only estimate is strictly more honest than showing neither, because the gap between them becomes visible rather than asserted.
Every value carries source: "measured". Anything unavailable is reported as
None with a reason, never as 0 — a zero in a memory panel reads as
“nothing used”, which would be a fresh lie in place of a missing number.
- veloxquant_mlx.ui.memory.memory_report(pid=None)[source]¶
Everything the panel’s memory card needs.
sourceis part of the payload rather than UI copy, so a consumer cannot render these numbers without also knowing they are measurements — and, by contrast, that the cache byte counters beside them are not.