In this article
SUPER does not expand the RTX 4070 beyond 12 GB; validate complete streams and scene fit with actual jobs.
Preserve the model and specification identity
The RTX 4070 SUPER is a separate Ada Lovelace GPU with 12 GB GDDR6X and reference board power of 220 W. The ordinary RTX 4070 occupies the same capacity class, so SUPER must not be interpreted as more model memory. The table describes one GPU and a reference configuration. Available memory depends on processes and display use. Record the exact AIB variant, especially when moving a workstation card into a server. Verify dimensions, power placement and airflow against that board rather than the architecture name alone. Inventory remains separate from measured workload behavior.
| Official variant | Memory per GPU | Memory type | Board power | Evidence |
|---|---|---|---|---|
| NVIDIA GeForce RTX 4070 SUPER — 12 GB NVIDIA comparison design | 12 GB | GDDR6X | 220 W | Specification |
Accept a complete inference response
Check vLLM requirements for the actual model revision, dtype and backend. Ada clears the hardware compute capability floor but does not certify every kernel. A useful RTX 4070 SUPER test fixes context, output limit and one streaming request. The worker must read beyond initial content to normal termination and available accounting information. If early fragments arrive but completion is missing, do not mark the whole request successful. Preserve peak memory and server outcome simultaneously to distinguish generation limits from a transport failure or incomplete client consumption in the examined scenario.
Verify Cycles through its output file
Blender documents CUDA and OptiX as GPU paths with system requirements. Run a packaged scene on the SUPER and confirm the intended GPU was used. Inspect the image alongside logs, because successful process exit does not establish the expected artifact is complete. Record system memory involvement separately from VRAM residency. RTX hardware tracing is available to a supporting backend rather than automatically to every renderer. This test promises no arbitrary frame duration and derives no performance from board power or gaming results. Preserve scene settings and assets for reproducible acceptance.
Keep server boundaries explicit
Associate manifests and file sources with both inference and rendering jobs. Record driver, software image, device identity and VRAM baseline on the host. When switching queues, confirm that the previous owner released resources rather than merely observing quiet HTTP traffic. One request’s peak memory does not establish safe concurrency for every future request. The 220 W specification excludes other server components and is not integrated job energy. Normal installation should work without disabling protections; investigate original logs, cooling, supply and the chosen software path first when instability appears instead of changing several settings at once.
Diagnose two kinds of completion
The artifact associates LLM terminal state and scene output with one pinned environment. If inference produces text without ending its stream, inspect client, proxy and engine lifecycle. If only rendering output is wrong, inspect assets and backend selection. If both fail during preparation, investigate their shared driver/device layer. This record describes the RTX 4070 SUPER for selected jobs. It establishes neither a universal client count nor gains over the ordinary RTX 4070, and a successful local launch does not confirm an external provider contract. Keep the accepted scenario and its limits together.
Coding LLMs on 12GB VRAM: Budget Context and Headroom · Planning a GPU pool: when is the next server actually needed? · GPU catalog