# NVIDIA H20: LLM inference and server rendering boundaries

NVIDIA H20: Official platform documentation distinguishes 96 GB and 141 GB H20 configurations. Capacity must follow the exact platform identity, not a generic H20 label.

Author: Retrivium team
Updated: 2026-11-02
Canonical URL: https://retrivium.ai/journal/nvidia-h20-llm-rendering/
Language: en

## Distinguish the documented memory configurations

NVIDIA trusted-computing release notes identify an HGX H20 A configuration with 96 GB HBM3 and an HGX H20 configuration with 141 GB HBM3e. That is platform-specific evidence, not permission to assign either value to every H20 device. The MIG guide also identifies a 96 GB H20. For an actual server, preserve the full platform designation and query the physical accelerator before selecting a capacity budget. Do not infer installed memory from a model-serving profile whose number may describe a runtime budget.

| Variant | Local memory, GB | Memory type | Published board power, W |
|---|---|---|---|
| HGX H20 A | 96 | HBM3 | Not verified |
| HGX H20 | 141 | HBM3e | Not verified |

The product or OEM specification establishes the configuration: [manufacturer source](https://docs.nvidia.com/595trd1-trusted-computing-solutions-release-notes.pdf).

## Separate architecture eligibility from model qualification

H20 uses a Hopper software path, but the selected inference package still needs explicit version and model validation. Record the CUDA runtime, driver, engine build, attention implementation and quantization. Run correctness checks at the intended context lengths rather than assuming that a neighbouring Hopper product proves the configuration. If a software matrix lists a particular H20 profile, retain the matrix version and exact profile name. It establishes the documented combination, not every model, all precisions or arbitrary future package releases.

The software boundary is documented in the [inference compatibility reference](https://docs.vllm.ai/en/stable/getting_started/installation/gpu/).

## Compare residency with identical serving limits

A comparison between the documented 96 GB and 141 GB configurations should hold checkpoint, input distribution, output limits and active-request targets constant. Measure allocations for weights, cache and engine workspaces separately. Where MIG is configured, use the assigned instance budget. Host RAM or the sum across an eight-device HGX node is not local memory on one accelerator. If a model spans devices, record its sharding and collective communication path instead of presenting the node total as an ordinary single-GPU fit.

## Do not infer a graphics stack from HBM capacity

The H20 documents used here describe a compute platform. They do not establish RTX ray-tracing hardware, an interactive display configuration or support for every renderer. Cycles must be assessed through its own supported CUDA or OptiX device path and driver requirements. Render the real scene and validate its features and output separately from inference. A large memory figure cannot compensate for an unsupported engine backend. Other rendering engines require their own current matrices rather than an assumption carried over from Blender.

Renderer requirements are separate in the [Cycles GPU manual](https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html).

## Keep uncertain board fields explicit

This guide leaves board power unresolved rather than importing a value from H100, H200 or another H20 description. Platform qualification should use the exact OEM power and cooling documentation. Retain firmware versions and visible device inventory with each result so the 96 GB and 141 GB systems cannot be confused later. Public platform documentation is useful planning evidence, but it does not establish current supply, an installed Retrivium configuration or approval of a provider endpoint by an external routing platform.

Related reading: [RAM and VRAM](/journal/ram-vs-vram/) and [a reproducible inference benchmark](/journal/inference-benchmark-method/). [GPU catalogue](/journal/nvidia-amd-gpu-catalog/) records the scope, model variants and unresolved specifications.

Additional primary references: [1](https://developer.nvidia.com/cuda/gpus), [2](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/supported-gpus.html).