on

Can the NVIDIA H200 NVL run Pixtral Large 124B (2411)?

75Great quality (A) · 75 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At Q5_K_M it needs about 98.6 GB of 141 GB usable, with an estimated speed of 39.3 tok/s.

Best quant
Q5_K_M
Generation speed
39.3 tok/s
Prompt processing
697 tok/s
First token (1K prompt)
1.5 s
Largest safe context
122K

Best app to run it on the NVIDIA H200 NVL

On Linux

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
vllm serve mistralai/Pixtral-Large-Instruct-2411
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • Docker Model Runner Handy if you already work in Docker.

On Windows

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • On Windows it runs through WSL2.
vllm serve mistralai/Pixtral-Large-Instruct-2411
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • Docker Model Runner Handy if you already work in Docker.

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Pixtral Large 124B (2411)

Original weights · Hugging Face

Full-precision files from Mistral AI, for fine-tuning, vLLM, Transformers.

huggingface.co/mistralai/Pixtral-Large-Instruct-2411 (opens in a new tab)

No sign-in needed.

Links checked 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 75Great quality (A) · 75 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q5_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great
How well it runs on the NVIDIA H200 NVL: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.34.0 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.14.9 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score88.9 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA H200 NVL

Quant Memory needed Available Speed Runs Quality Download
Q2_K 60.2 GB 141 GB 78.0 tok/s Runs great 54Fair quality (C) · 54 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q3_K_M 71.4 GB 141 GB 61.4 tok/s Runs great 65Good quality (B) · 65 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q4_K_M 86.2 GB 141 GB 47.5 tok/s Runs great 74Great quality (A) · 74 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 98.6 GB 141 GB 39.3 tok/s Runs great 75Great quality (A) · 75 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 112 GB 141 GB 33.0 tok/s Runs great 77Great quality (A) · 77 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 142 GB 141 GB 15.5 tok/s Runs welloffloads to RAM 78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 259 GB 141 GB — Won't run 78Great quality (A) · 78 of 100: how capable the model is at F16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?