Can Qwen3.5 397B A17B run on NVIDIA H200 PCIe 141GB?

NO — Won't Fit

F0Won't run

○Estimated from fit model

Qwen3.5 397B A17B needs ~304.0 GB but NVIDIA H200 PCIe 141GB only has 141.0 GB. Try a smaller quantization or lighter model.

Runtime: OllamaCapacity: No fitBandwidth: HighStack: BasicBottleneck: Memory capacity

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

Q4_K_M (Medium quality) — 304.0 GB, exceeds 141.0 GB available

304.0 GB required141.0 GB available

216% VRAM needed

163.0 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.7 tok/s

TTFT

72886 ms

Safe context

Memory

304.0 GB / 141.0 GB

Offload

50%

Memory breakdown

Weights242.2 GB

KV Cache46.5 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 397B A17B on NVIDIA H200 PCIe 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: 2.7 tok/s decode · 72.9s TTFT (warm) · 7 tok/s prefill

What limits this setup

Usable VRAM is the main blocker for this model.

Not enough usable memory

The model needs 304.0 GB, but this setup only exposes 141.0 GB of usable VRAM.

Best improvement path

Add more VRAM headroom

The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	F	Too heavy	3.1 tok/s	33797 ms	4K
Coding	F	Too heavy	2.7 tok/s	72886 ms	4K
Agentic Coding	F	Too heavy	2.5 tok/s	112756 ms	4K
Reasoning	F	Too heavy	2.7 tok/s	86139 ms	4K
RAG	F	Too heavy	2.5 tok/s	140946 ms	4K

Quantization options

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

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	154.8 GB	Low	F0
Q3_K_S	3	194.5 GB	Low	F0
NVFP4	4	222.3 GB	Medium	F0
Q4_K_M	4	242.2 GB	Medium	F0
Q5_K_M	5	285.8 GB	High	F0
Q6_K	6	325.5 GB	High	F0
Q8_0	8	424.8 GB	Very High	F0
F16	16	813.8 GB	Maximum	F0