Can Qwen 3.5 397B A17B run on H100 NVL 188GB?

Q: What should I upgrade first if Qwen 3.5 397B A17B feels slow on H100 NVL 188GB?

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

YES — With Q3_K_S

S86Excellent

Estimated from fit model

Qwen 3.5 397B A17B needs ~217.1 GB VRAM. H100 NVL 188GB has 188.0 GB. With Q3_K_S quantization, expect ~67 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: HighStack: StandardBottleneck: Host offload

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.

Qwen 3.5 397B A17B at Q4_K_M needs 264.7 GB — too much for H100 NVL 188GB (188.0 GB). Runs at Q3_K_S (217.1 GB) with low quality. 2 quantization levels fit.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 264.7 GB, exceeds 188.0 GB available

264.7 GB required188.0 GB available

141% VRAM needed

76.7 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

41.4 tok/s

TTFT

4677 ms

Safe context

Memory

264.7 GB / 188.0 GB

Offload

30%

Memory breakdown

Weights242.2 GB

KV Cache2.9 GB

Runtime0.9 GB

Headroom18.8 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsQwen 3.5 397B A17B on H100 NVL 188GB
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: 41.4 tok/s decode · 4.7s TTFT (warm) · 104 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

Best improvement path

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Increase host RAM if you keep offloading

This setup may need roughly 26.1 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	F	Too heavy	41.8 tok/s	2528 ms	4K
Coding	F	Too heavy	41.4 tok/s	4677 ms	4K
Agentic Coding	F	Too heavy	40.7 tok/s	6925 ms	4K
Reasoning	F	Too heavy	41.4 tok/s	5527 ms	4K
RAG	F	Too heavy	40.7 tok/s	8656 ms	4K

Quantization options

How Qwen 3.5 397B A17B (397B params) fits at each quantization level on H100 NVL 188GB (188.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

Get started

Copy-paste commands to run Qwen 3.5 397B A17B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
  --hf-repo "Qwen/Qwen3.5-397B-A17B-Instruct" \
  --hf-file "Qwen3.5-397B-A17B-Instruct-Q4_K_M.gguf" \
  -c 4096 -ngl 99

Upgrade options

Hardware that runs Qwen 3.5 397B A17B well

AMD Instinct MI350X 288GBBudget pick

288 GB VRAM (+100)8000 GB/s (+200)

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 (+68)

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.

Adds memory headroom for longer context windows and future model growth.

~$20,000 MSRP

Frequently asked questions

Can H100 NVL 188GB run Qwen 3.5 397B A17B?

Yes, H100 NVL 188GB can run Qwen 3.5 397B A17B at Q3_K_S quantization (Very compromised (needs ~26.1 GB host RAM)). The recommended Q4_K_M requires 264.7 GB which exceeds available memory, but at Q3_K_S it needs only 217.1 GB. Expected decode speed: 66.5 tok/s.

How much VRAM does Qwen 3.5 397B A17B need?

Qwen 3.5 397B A17B (397B parameters) requires approximately 264.7 GB at Q4_K_M quantization. On H100 NVL 188GB, it fits at Q3_K_S using 217.1 GB.

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

The recommended quantization is Q4_K_M, but on H100 NVL 188GB the best fitting quantization is Q3_K_S, which uses 217.1 GB.

What speed will Qwen 3.5 397B A17B run at on H100 NVL 188GB?

On H100 NVL 188GB, Qwen 3.5 397B A17B achieves approximately 66.5 tokens per second decode speed with a time-to-first-token of 2912ms using Q3_K_S quantization.

Can H100 NVL 188GB run Qwen 3.5 397B A17B for coding?

For coding workloads, Qwen 3.5 397B A17B on H100 NVL 188GB receives a F grade with 41.4 tok/s and 4K context.

What context window can Qwen 3.5 397B A17B use on H100 NVL 188GB?

On H100 NVL 188GB, Qwen 3.5 397B A17B can safely use up to 4K tokens of context at Q3_K_S quantization. The model's official context limit is 131K, but available memory constrains the safe maximum.

See all results for H100 NVL 188GB 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-h100-nvl-188gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: