Will It Run AI

Can Llama 4 Maverick 17B 128E run on NVIDIA H200 PCIe 141GB?

NO — Won't Fit

F0Won't run
Estimated from fit model

Llama 4 Maverick 17B 128E needs ~261.9 GB but NVIDIA H200 PCIe 141GB only has 141.0 GB. Try a smaller quantization or lighter model.

Runtime: llama.cppCapacity: No fitBandwidth: HighStack: StandardBottleneck: Memory capacity
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

Q4_K_M (Medium quality) 261.9 GB, exceeds 141.0 GB available
261.9 GB required141.0 GB available
186% VRAM needed

120.9 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

11.6 tok/s

TTFT

16761 ms

Safe context

4K

Memory

261.9 GB / 141.0 GB

Offload

50%

Memory breakdown

Weights244.0 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 feelsLlama 4 Maverick 17B 128E on NVIDIA H200 PCIe 141GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step. Given information: - Speed = 60 mph (miles per hour) - Time = 2.5 hours Formula: Distance = Speed x Time Calculation: Distance = 60 mph x 2.5 h = 150 miles The train travels 150 miles. Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time. Breakdown: - First half: 1.25 hours at 60 mph = 75 miles - Stop: 20 minutes (no distance) - Second half: 1.25 hours at 60 mph = 75 miles Total distance: 150 miles (same) Total time: 2.5 h + 0.33 h = 2.83 hours Average speed: 150 / 2.83 = 53 mph The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 11.6 tok/s decode · 16.8s TTFT (warm) · 29 tok/s prefill

What limits this setup

Usable VRAM is the main blocker for this model.

Not enough usable memory

The model needs 261.9 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

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy11.7 tok/s9038 ms4K
CodingFToo heavy11.6 tok/s16761 ms4K
Agentic CodingFToo heavy11.3 tok/s24939 ms4K
ReasoningFToo heavy11.6 tok/s19808 ms4K
RAGFToo heavy11.3 tok/s31173 ms4K

Quantization options

How Llama 4 Maverick 17B 128E (400B params) fits at each quantization level on NVIDIA H200 PCIe 141GB (141.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
156.0 GB
LowF0
Q3_K_S
3
196.0 GB
LowF0
NVFP4
4
224.0 GB
MediumF0
Q4_K_M
4
244.0 GB
MediumF0
Q5_K_M
5
288.0 GB
HighF0
Q6_K
6
328.0 GB
HighF0
Q8_0
8
428.0 GB
Very HighF0
F16
16
820.0 GB
MaximumF0

Opções de upgrade

Hardware que roda bem Llama 4 Maverick 17B 128E

Frequently asked questions

Can NVIDIA H200 PCIe 141GB run Llama 4 Maverick 17B 128E?

No, Llama 4 Maverick 17B 128E requires more memory than NVIDIA H200 PCIe 141GB provides.

How much VRAM does Llama 4 Maverick 17B 128E need?

Llama 4 Maverick 17B 128E (400B parameters) requires approximately 261.9 GB of memory with Q4_K_M quantization.

What is the best quantization for Llama 4 Maverick 17B 128E?

The recommended quantization for Llama 4 Maverick 17B 128E is Q4_K_M, which balances quality and memory efficiency.

What speed will Llama 4 Maverick 17B 128E run at on NVIDIA H200 PCIe 141GB?

On NVIDIA H200 PCIe 141GB, Llama 4 Maverick 17B 128E achieves approximately 11.6 tokens per second decode speed with a time-to-first-token of 16761ms using Q4_K_M quantization.

Can NVIDIA H200 PCIe 141GB run Llama 4 Maverick 17B 128E for coding?

For coding workloads, Llama 4 Maverick 17B 128E on NVIDIA H200 PCIe 141GB receives a F grade with 11.6 tok/s and 4K context.

What context window can Llama 4 Maverick 17B 128E use on NVIDIA H200 PCIe 141GB?

On NVIDIA H200 PCIe 141GB, Llama 4 Maverick 17B 128E can safely use up to 4K tokens of context. The model's official context limit is 1.0M, but available memory constrains the safe maximum.

What should I upgrade first if Llama 4 Maverick 17B 128E feels slow on NVIDIA H200 PCIe 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.

See all results for NVIDIA H200 PCIe 141GBSee all hardware for Llama 4 Maverick 17B 128E
Embed this result

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

<iframe src="https://willitrunai.com/embed/llama-4-maverick-17b-128e-on-h200-pcie-141gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: