The NVIDIA GH200 Grace Hopper Superchip is a unique CPU+GPU module that combines a 72-core ARM Grace CPU and an H100 Hopper GPU on a single package connected by 900 GB/s NVLink-C2C. The GPU's 96 GB of HBM3 can directly and coherently access the 480 GB of LPDDR5X CPU memory, giving the GH200 an effective memory pool of up to 624 GB — enough to run 70B models at FP16 with substantial KV cache without any model sharding. Lambda AI benchmarks showed a single GH200 delivering 7.6x the inference throughput of a single H100 SXM for Llama 3.1 70B due to this unified memory advantage.
Beyond LLMs
AI Capability Matrix
What AI tasks this GPU can handle — from text generation to image and video creation.
96 GB HBM3 GPU memory + 480 GB LPDDR5X CPU memory (coherent unified pool)4,000 GB/s HBM3 bandwidth900 GB/s NVLink-C2C CPU-GPU interconnect — 7x faster than PCIe Gen572-core ARM Neoverse V2 (Grace) CPU integrated on-moduleHopper Transformer Engine with FP8 support~900W total module TDP
Für KI-Workloads
Stärken
Unified coherent memory (96 GB HBM + 480 GB LPDDR5X) eliminates GPU memory capacity bottleneck for large models
Up to 7.6x higher Llama 70B throughput vs. a single H100 SXM by keeping model and KV cache fully in-memory
Eliminates PCIe bottleneck with 900 GB/s NVLink-C2C between CPU and GPU
Well-suited for long-context inference where KV cache growth exhausts standard 80 GB HBM
Hinweise
Non-standard form factor — requires Grace Hopper-specific server nodes, not standard x86 infrastructure
LPDDR5X CPU memory bandwidth (512 GB/s) is much lower than HBM — performance varies by model offloading pattern
High cost and limited availability; predominantly available on specialized cloud instances
ARM-based Grace CPU requires some software stack compatibility verification for x86-native tooling
Architecture
Hopper
Hopper is NVIDIA's datacenter-focused architecture succeeding Ampere. Built on TSMC 4N, it introduces the Transformer Engine with automatic FP8/FP16 mixed-precision training, HBM3/HBM3e memory, and NVLink 4.0 for multi-GPU scaling. The H100 flagship delivers up to 3x the AI training performance of A100.
AI Relevance
The Transformer Engine automatically manages FP8 precision for optimal training speed without accuracy loss. With up to 141 GB HBM3e (H200), Hopper GPUs can hold the largest open-weight models entirely in GPU memory, making them the workhorse of AI datacenters.
Qwen 3.5 27B matches Chat and keeps a practical fit profile. It is a recent-generation family, which helps on current local SOTA workloads. It fits natively with comfortable headroom. Context coverage stays within the requested workload envelope. Known distribution channels: huggingface, ollama, lm-studio.
Qwen3-Coder-Next is a specialized fit for Coding. It is a recent-generation family, which helps on current local SOTA workloads. It fits natively with comfortable headroom. Context coverage stays within the requested workload envelope. Known distribution channels: huggingface, ollama, lm-studio.
Qwen3-Coder-Next is a specialized fit for Agentic Coding. It is a recent-generation family, which helps on current local SOTA workloads. It fits natively with comfortable headroom. Context coverage stays within the requested workload envelope. Known distribution channels: huggingface, ollama, lm-studio.
Qwen3-Coder-Next matches Reasoning and keeps a practical fit profile. It is a recent-generation family, which helps on current local SOTA workloads. It fits natively with comfortable headroom. Context coverage stays within the requested workload envelope. Known distribution channels: huggingface, ollama, lm-studio.
Qwen 3.5 27B matches RAG and keeps a practical fit profile. It is a recent-generation family, which helps on current local SOTA workloads. It fits natively with comfortable headroom. Context coverage stays within the requested workload envelope. Known distribution channels: huggingface, ollama, lm-studio.
Image models estimated at 1024×1024 (28 steps, FP16). Video models estimated at 768×512 (25 frames, 30 steps, FP16). Actual performance varies with runtime and system load.
Multi-GPU scaling
NVIDIA GH200 96GB — Up to 2× via NVLink
Scale out with multiple GPUs for larger models. NVLink provides 900 GB/s inter-GPU bandwidth with 8% overhead.
Config
Effective memory
Models that fit
Est. bandwidth
1× NVIDIA
96 GB
351/374
4,000 GB/s
2× NVIDIA
192 GB
359/374
7,360 GB/s
Model counts use default quantization at coding workload settings. Multi-GPU scaling factor: 0.92× per additional GPU.
NVIDIA GH200 96GB (96 GB VRAM) can run these top models: Qwen 3.5 122B A10B (score: 96/100), Qwen3-Coder-Next (score: 95/100), Qwen 2.5 VL 72B (score: 95/100). See the full compatibility list above.
How much VRAM does NVIDIA GH200 96GB have for AI?
NVIDIA GH200 96GB has 96 GB of VRAM available for AI model inference. This determines which models and quantization levels you can run locally.
Is NVIDIA GH200 96GB good for running LLMs locally?
Yes, NVIDIA GH200 96GB is excellent for running LLMs locally with top compatibility scores above 80/100.
What is the best model for NVIDIA GH200 96GB for coding?
For coding on NVIDIA GH200 96GB, we recommend Qwen3-Coder-Next. It achieves 218.8 tokens per second with 256K context window. Qwen3-Coder-Next is a specialized fit for Coding. It is a recent-generation family, which helps on current local SOTA workloads. It fits natively with comfortable headroom. Context coverage stays within the requested workload envelope. Known distribution channels: huggingface, ollama, lm-studio.
Should I upgrade from NVIDIA GH200 96GB?
There are 5 upgrade path(s) from NVIDIA GH200 96GB: NVIDIA GH200 96GB, NVIDIA H200 141GB. Upgrading would unlock larger models and faster inference speeds.
Can NVIDIA GH200 96GB run Flux for image generation?
Yes, NVIDIA GH200 96GB with 96 GB of usable memory can run Flux.1 Dev at FP16 natively. Flux is a 12B parameter diffusion transformer that produces high-quality images. You can also run the Schnell variant for faster generation.
What image and video AI models can I run on NVIDIA GH200 96GB?
NVIDIA GH200 96GB (96 GB VRAM) can handle various AI generation tasks beyond LLMs. For image generation, SDXL and Stable Diffusion 3.5 run well. Flux.1 Dev also runs natively for state-of-the-art image quality. For video, LTX Video 2.3 can generate short clips. Check the AI Capability Matrix above for detailed compatibility.
Is NVIDIA GH200 96GB good for AI image generation?
NVIDIA GH200 96GB is excellent for AI image generation. With 96 GB of usable memory, it runs all major diffusion models including Flux.1, SDXL, and Stable Diffusion 3.5 at full precision. You can generate high-resolution images quickly and even handle video generation models.
Can NVIDIA GH200 96GB run Qwen 3.5 27B?
Yes, NVIDIA GH200 96GB with 96 GB of usable memory can run Qwen 3.5 27B at Q8 (near-lossless, ~28.9 GB) or even FP16 (~55.4 GB) depending on your context needs. This setup provides an excellent experience with this model. Use Ollama or vLLM for best results.
What is the best quantization for AI models on NVIDIA GH200 96GB?
With 96 GB VRAM on NVIDIA GH200 96GB, use Q8_0 for most models — it is near-lossless and you have the memory for it. For 70B+ models, Q6_K offers excellent quality. Reserve Q4_K_M for 100B+ models or when you need maximum context length.
For local LLMs on NVIDIA GH200 96GB, does VRAM matter more than bandwidth?
NVIDIA GH200 96GB already has strong memory bandwidth, so the next limit is often memory capacity and context headroom rather than raw decode speed. For local LLMs, fit first and bandwidth second is the right mental model.
How does multi-GPU scale for AI inference on NVIDIA GH200 96GB?
NVIDIA GH200 96GB supports up to 2× GPU scaling via NVLink at 900 GB/s. With 2× GPUs, you get 192 GB effective memory with a 0.92× scaling factor per GPU. This enables running models like Qwen 3.5 397B A17B and Kimi K2.5 that don't fit on a single card.
Is NVLink required for multi-GPU NVIDIA GH200 96GB inference?
NVLink is recommended for NVIDIA GH200 96GB multi-GPU inference, providing 900 GB/s interconnect bandwidth with only 8% scaling overhead. PCIe-only setups work but have higher overhead (~25%) due to limited inter-GPU bandwidth.