Can Qwen3.5 122B A10B run on NVIDIA GH200 96GB?

YES — Tight Fit

C52Usable

Estimated from fit model

Qwen3.5 122B A10B needs ~84.9 GB VRAM. NVIDIA GH200 96GB has 96.0 GB. With Q3_K_M quantization, expect ~50 tok/s.

Runtime: OllamaCapacity: TightBandwidth: HighStack: BasicBottleneck: Balanced

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

F16 (Maximum quality) — 275.2 GB, exceeds 96.0 GB available

275.2 GB required96.0 GB available

287% VRAM needed

179.2 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.7 tok/s

TTFT

71136 ms

Safe context

Memory

275.2 GB / 96.0 GB

Offload

70%

Memory breakdown

Weights250.1 GB

KV Cache14.3 GB

Runtime1.2 GB

Headroom9.6 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsQwen3.5 122B A10B on NVIDIA GH200 96GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API.

When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed.

Key benefits of running locally:
  - Full privacy: your prompts never leave your machine
  - No per-token cost or rate limits
  - Works offline once the model is downloaded
  - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb:

  Model size     Q4 (4-bit)    Q8 (8-bit)    FP16
  7B params      ~4.3 GB       ~7.5 GB       ~14 GB
  13B params     ~7.9 GB       ~13.9 GB      ~26 GB
  70B params     ~42.7 GB      ~74.9 GB      ~140 GB

Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 2.7 tok/s decode · 71.1s TTFT (warm) · 7 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

No major red flags

This recommendation has enough memory headroom and acceptable estimated speed for the selected workload.

Best improvement path

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	B	Runs well	50.4 tok/s	2095 ms	28K
Coding	C	Tight fit	50.4 tok/s	3841 ms	28K
Agentic Coding	C	Runs with offload (needs ~1.9 GB host RAM)	40.7 tok/s	6911 ms	28K
Reasoning	C	Tight fit	50.4 tok/s	4539 ms	28K
RAG	C	Runs with offload (needs ~1.9 GB host RAM)	40.7 tok/s	8639 ms	28K

Quantization options

How Qwen3.5 122B A10B (122B params) fits at each quantization level on NVIDIA GH200 96GB (96.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	47.6 GB	Low	C48
Q3_K_S	3	59.8 GB	Low	C48
NVFP4	4	68.3 GB	Medium	C48
Q4_K_MBest for your GPU	4	74.4 GB	Medium	C48
Q5_K_M	5	87.8 GB	High	F0
Q6_K	6	100.0 GB	High	F0
Q8_0	8	130.5 GB	Very High	F0
F16	16	250.1 GB	Maximum	F0

Get started

Copy-paste commands to run Qwen3.5 122B A10B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
  --hf-repo "unsloth/Qwen3.5-122B-A10B-GGUF" \
  --hf-file "Qwen3.5-122B-A10B-GGUF-Q3_K_M.gguf" \
  -c 4096 -ngl 99

Opciones de mejora

Hardware que ejecuta bien Qwen3.5 122B A10B

NVIDIA H200 141GBOpción económica

141 GB VRAM (+45)4800 GB/s (+800)

Añade margen de memoria para más contexto y para que el modelo envejezca mejor.62.7 tok/s decodificación

Añade margen de memoria para más contexto y para que el modelo envejezca mejor.

~$30,000 MSRP

NVIDIA H200 PCIe 141GBMejor relación calidad-precio

141 GB VRAM (+45)4800 GB/s (+800)

Añade margen de memoria para más contexto y para que el modelo envejezca mejor.62.7 tok/s decodificación

Añade margen de memoria para más contexto y para que el modelo envejezca mejor.

~$30,000 MSRP

NVIDIA B200 180GBMejora NVIDIA

180 GB VRAM (+84)8000 GB/s (+4000)

Sube la velocidad estimada de decodificación alrededor de un 107%.104.5 tok/s decodificación

Sube la velocidad estimada de decodificación alrededor de un 107%.

Añade margen de memoria para más contexto y para que el modelo envejezca mejor.

~$30,000 MSRP

Frequently asked questions

Can NVIDIA GH200 96GB run Qwen3.5 122B A10B?

Yes, NVIDIA GH200 96GB can run Qwen3.5 122B A10B with a C grade (Tight fit). Expected decode speed: 50.4 tok/s.

How much VRAM does Qwen3.5 122B A10B need?

Qwen3.5 122B A10B (122B parameters) requires approximately 84.9 GB of memory with Q3_K_M quantization.

What is the best quantization for Qwen3.5 122B A10B?

The recommended quantization for Qwen3.5 122B A10B is Q3_K_M, which balances quality and memory efficiency.

What speed will Qwen3.5 122B A10B run at on NVIDIA GH200 96GB?

On NVIDIA GH200 96GB, Qwen3.5 122B A10B achieves approximately 50.4 tokens per second decode speed with a time-to-first-token of 3841ms using Q3_K_M quantization.

Can NVIDIA GH200 96GB run Qwen3.5 122B A10B for coding?

For coding workloads, Qwen3.5 122B A10B on NVIDIA GH200 96GB receives a C grade with 50.4 tok/s and 28K context.

What context window can Qwen3.5 122B A10B use on NVIDIA GH200 96GB?

On NVIDIA GH200 96GB, Qwen3.5 122B A10B can safely use up to 28K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

See all results for NVIDIA GH200 96GB See all hardware for Qwen3.5 122B A10B

Embed this result▼

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/hf-unsloth--qwen3-5-122b-a10b-gguf-on-gh200-96gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: