Can Qwen 3.5 397B A17B run on NVIDIA H200 141GB?

Q: What should I upgrade first if Qwen 3.5 397B A17B feels slow on NVIDIA H200 141GB?

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.

NO — Won't Fit

F0Won't run

Estimated from fit model

Qwen 3.5 397B A17B needs ~260.0 GB but NVIDIA H200 141GB only has 141.0 GB. Try a smaller quantization or lighter model.

Runtime: llama.cppCapacity: No fitBandwidth: HighStack: StandardBottleneck: 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) — 260.0 GB, exceeds 141.0 GB available

260.0 GB required141.0 GB available

184% VRAM needed

119.0 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

16.9 tok/s

TTFT

11438 ms

Safe context

Memory

260.0 GB / 141.0 GB

Offload

50%

Memory breakdown

Weights242.2 GB

KV Cache2.9 GB

Runtime0.9 GB

Headroom14.1 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsQwen 3.5 397B A17B on NVIDIA H200 141GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort:

def quicksort(arr):
    if len(arr) <= 1:
        return arr
    pivot = arr[len(arr) // 2]
    left   = [x for x in arr if x < pivot]
    middle = [x for x in arr if x == pivot]
    right  = [x for x in arr if x > pivot]
    return quicksort(left) + middle + quicksort(right)

# Example usage
numbers = [3, 6, 8, 10, 1, 2, 1]
print(quicksort(numbers))  # [1, 1, 2, 3, 6, 8, 10]

The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]:
    """Sort a list using the quicksort algorithm.

    Args:
        arr: List of integers to sort.

    Returns:
        A new sorted list.
    """
    if len(arr) <= 1:
        return arr
    pivot = arr[len(arr) // 2]
    left   = [x for x in arr if x < pivot]
    middle = [x for x in arr if x == pivot]
    right  = [x for x in arr if x > pivot]
    return quicksort(left) + middle + quicksort(right)

Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 16.9 tok/s decode · 11.4s TTFT (warm) · 42 tok/s prefill

What limits this setup

Usable VRAM is the main blocker for this model.

Not enough usable memory

The model needs 260.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	17.1 tok/s	6182 ms	4K
Coding	F	Too heavy	16.9 tok/s	11438 ms	4K
Agentic Coding	F	Too heavy	16.6 tok/s	16941 ms	4K
Reasoning	F	Too heavy	16.9 tok/s	13518 ms	4K
RAG	F	Too heavy	16.6 tok/s	21176 ms	4K

Quantization options

How Qwen 3.5 397B A17B (397B params) fits at each quantization level on NVIDIA H200 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

Upgrade options

Hardware that runs Qwen 3.5 397B A17B well

AMD Instinct MI350X 288GBBudget pick

288 GB VRAM (+147)8000 GB/s (+3200)

Makes the model fit on the accelerator instead of staying completely out of reach.78.9 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$8,000 MSRP

AMD Instinct MI325X 256GBBest value

256 GB VRAM (+115)6000 GB/s (+1200)

Makes the model fit on the accelerator instead of staying completely out of reach.39.2 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Raises estimated decode speed by about 132%.

~$20,000 MSRP

Frequently asked questions

Can NVIDIA H200 141GB run Qwen 3.5 397B A17B?

No, Qwen 3.5 397B A17B requires more memory than NVIDIA H200 141GB provides.

How much VRAM does Qwen 3.5 397B A17B need?

Qwen 3.5 397B A17B (397B parameters) requires approximately 260.0 GB of memory with Q4_K_M quantization.

What is the best quantization for Qwen 3.5 397B A17B?

The recommended quantization for Qwen 3.5 397B A17B is Q4_K_M, which balances quality and memory efficiency.

What speed will Qwen 3.5 397B A17B run at on NVIDIA H200 141GB?

On NVIDIA H200 141GB, Qwen 3.5 397B A17B achieves approximately 16.9 tokens per second decode speed with a time-to-first-token of 11438ms using Q4_K_M quantization.

Can NVIDIA H200 141GB run Qwen 3.5 397B A17B for coding?

For coding workloads, Qwen 3.5 397B A17B on NVIDIA H200 141GB receives a F grade with 16.9 tok/s and 4K context.

What context window can Qwen 3.5 397B A17B use on NVIDIA H200 141GB?

On NVIDIA H200 141GB, Qwen 3.5 397B A17B can safely use up to 4K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.

What should I upgrade first if Qwen 3.5 397B A17B feels slow on NVIDIA H200 141GB?

See all results for NVIDIA H200 141GB See all hardware for Qwen 3.5 397B A17B

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/qwen-3.5-397b-a17b-on-h200-141gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: