In this article
A GPU can consume VRAM for display, driver and other processes before a model loads. Compare a workstation with a headless node using a measured baseline, not nominal capacity. Display attached and display active represent different states.
A GPU can consume VRAM for display, driver and other processes before a model loads. Compare a workstation with a headless node using a measured baseline, not nominal capacity. Display attached and display active represent different states.
Capture pre-start state
Record UUID, model, driver, OS, total/used/free memory and available process observations. Take several samples after the environment settles. A compositor, browser and other programs can change consumption without model activity. Do not close a user’s applications outside an authorized window; use observation or a separate test profile. Advertised capacity is not guaranteed free memory for a new compute process at startup.
Separate attachment and activity
Nvidia-smi defines Display Attached as physical connection and Display Active as initialized display state with allocated resources. Display can remain active without a physically attached monitor. Unplugging a cable therefore does not establish that all display-related VRAM was released. Account for field support and tool-version changes. Preserve N/A or query status instead of converting missing data to Disabled or zero.
Measure the model increment
An illustrative report captures baseline, starts a fixed workload and observes memory in the same scope. The difference describes change but may not belong entirely to the model if desktop activity changed simultaneously. Use controlled conditions and retain neighboring-process observations. Do not calculate “available VRAM” by subtracting an assumed universal display reserve from advertised capacity.
| Stage | Evidence |
|---|---|
| Before loading | Display state and memory baseline |
| During loading | Peak and current consumption |
| Steady operation | Matched-workload change |
| After exit | Residual usage and other clients |
Compare environments fairly
Preserve OS, driver and memory-management differences between workstation and headless systems. NVML memory and process reporting has product and mode limitations, so equal visibility cannot be promised across platforms. Missing per-process memory is not zero consumption. If a workload fits only on the headless system, inspect the actual baseline and other memory boundaries. A small successful request does not establish headroom for larger context or more concurrent work.
Test baseline repeatability
Repeat after ordinary environment startup and model shutdown. Retain the observed residual range rather than one favorable minimum. The artifact should show display flags, aggregate memory and process-visibility limitations. For sustained placement, use a verified operating mode with known neighboring workloads. This explains differences between nominally identical GPUs without inventing universal reserves or promising that disconnecting a display makes all VRAM available to inference. Recheck after desktop or driver updates, since baseline behavior can change without replacing the GPU. A repeated baseline is stronger evidence than one idle screenshot.
Related operational reading: studio workstations night; rtx for inference.