Hugpy Wrapper / System observability

Live activity

Recorded evidence and the machine, side by side.
Database inspector ↗Connecting…
Resolving active database…
SYSTEM CPU
—
Waiting for two samples
SYSTEM RAM · TOTAL − AVAILABLE
—
/proc/meminfo
GPU MEMORY · ALL NVIDIA CARDS
—
Waiting for driver
WRAPPER ACTIVITY · SELECTED WORKER
—
Recorded call and resident state

Recent system activity

SystemDatabaseUp to 120 samples
CPU utilization · entire host0–100%
RAM used · system and recorded host state

Database ↔ system comparison

Difference = system − database · same-unit values only
MeasurementDatabaseSystem nowDifferenceDB ageSource

Database state is event-driven: an old timestamp can mean the value has not changed. GPU matching uses UUID, not card order. CPU utilization covers the whole host; wrapper CPU allocations have a different scope. Samples are close in time, not atomic across the database and OS.

Resident processes

DB memory is the wrapper’s accounting; OS RSS includes shared/file-backed pages.
ModelPID / processDB stateDB VRAMDB RAMOS RSSOS anonymousCPU affinityDB age
Process samples are matched by PID and may be unavailable after exit or due to permissions. A PID alone does not establish process identity.
Click a row for the full captured record. Changed values flash green. Calls include the latest 100 records plus up to 100 active records; other tables show up to 100. Request and response bodies are excluded.

Captured record