VOOZH about

URL: https://willitrunai.com/can-run/hf-unsloth--qwen3-5-122b-a10b-gguf-on-h200-141gb


Can Qwen3.5 122B A10B run on NVIDIA H200 141GB?

YES — Runs Great

C55Usable
Estimated from fit model

Qwen3.5 122B A10B needs ~89.4 GB VRAM. NVIDIA H200 141GB has 141.0 GB. With Q3_K_M quantization, expect ~63 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: HighStack: BasicBottleneck: Balanced
Share:

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) — 279.7 GB, exceeds 141.0 GB available
279.7 GB required141.0 GB available
198% VRAM needed

138.7 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

6.2 tok/s

TTFT

31137 ms

Safe context

4K

Memory

279.7 GB / 141.0 GB

Offload

50%

Memory breakdown

Weights250.1 GB
KV Cache14.3 GB
Runtime1.2 GB
Headroom14.1 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsQwen3.5 122B A10B on NVIDIA H200 141GB
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: 6.2 tok/s decode · 31.1s TTFT (warm) · 16 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

WorkloadGradeFitDecodeTTFTContext
ChatCRuns well62.7 tok/s1684 ms74K
CodingCRuns well62.7 tok/s3086 ms74K
Agentic CodingBRuns well62.7 tok/s4489 ms74K
ReasoningCRuns well62.7 tok/s3648 ms74K
RAGBRuns well62.7 tok/s5612 ms74K

Quantization options

How Qwen3.5 122B A10B (122B params) fits at each quantization level on NVIDIA H200 141GB (141.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
47.6 GB
LowC44
Q3_K_S
3
59.8 GB
LowC46
NVFP4
4

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

Frequently asked questions

See all results for NVIDIA H200 141GBSee all hardware for Qwen3.5 122B A10B
68.3 GB
Medium
C47
Q4_K_M
4
74.4 GB
MediumC48
Q5_K_M
5
87.8 GB
HighC48
Q6_KBest for your GPU
6
100.0 GB
HighC48
Q8_0
8
130.5 GB
Very HighF0
F16
16
250.1 GB
MaximumF0