on

Can the NVIDIA H200 NVL run Devstral 2 (123B)?

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

Yes, it runs great

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

Best quant
Q5_K_M
Generation speed
38.9 tok/s
Prompt processing
691 tok/s
First token (1K prompt)
1.5 s
Largest safe context
120K

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/Devstral-2-123B-Instruct-2512
  • Ollama One command with Ollama’s own build of this model.
  • LM Studio Point-and-click: search, download and chat in one window.

On Windows

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

  • One command with Ollama’s own build of this model.
  • Serves an OpenAI-compatible API that other apps and coding tools can use.
ollama run devstral-2:123b
  • LM Studio Point-and-click: search, download and chat in one window.
  • llama.cpp Usually the first to support new model architectures.

Want an agent? Devstral 2 (123B) supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

Reverse engineering? Serve Devstral 2 (123B) locally and use it from Ghidra, IDA Pro, Binary Ninja, radare2 or JADX with one of these:

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 Devstral 2 (123B)

Recommended for the NVIDIA H200 NVL: Q5_K_M. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run devstral-2:123b

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q5_K_M files (opens in a new tab)

huggingface.co/unsloth/Devstral-2-123B-Instruct-2512-GGUF (opens in a new tab)

ollama run hf.co/unsloth/Devstral-2-123B-Instruct-2512-GGUF

Original weights · Hugging Face

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

huggingface.co/mistralai/Devstral-2-123B-Instruct-2512 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Mistral AI. The weights themselves download from Hugging Face.

github.com/mistralai/mistral-inference (opens in a new tab)

Mistral AI’s official inference code.

git clone https://github.com/mistralai/mistral-inference

How it’s rated

Quality 83Great quality (A) · 83 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 92/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.37.5 / 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.8 / 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 score92.3 / 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.6 GB 141 GB 77.4 tok/s Runs great 60Good quality (B) · 60 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 71.9 GB 141 GB 60.9 tok/s Runs great 72Great quality (A) · 72 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q4_K_M 86.9 GB 141 GB 47.1 tok/s Runs great 81Great quality (A) · 81 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q5_K_M 99.4 GB 141 GB 38.9 tok/s Runs great 83Great quality (A) · 83 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q6_K 113 GB 141 GB 32.7 tok/s Runs great 85Excellent quality (A+) · 85 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q8_0 143 GB 141 GB 11.2 tok/s Runs welloffloads to RAM 86Excellent quality (A+) · 86 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
F16 261 GB 141 GB — Won't run 86Excellent quality (A+) · 86 of 100: how capable the model is at F16, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab) 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?