Can I run Devstral 2 123B?
Devstral 2 123B by Mistral AI needs around 96 GB of RAM at the recommended 4-bit quantization (74.6 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~5 tok/s on a Apple M-series Max.
Reading your hardware signalsβ¦
Real-world notes
Devstral 2 123B is Mistral's big dense coding model, and it is squarely for people building serious local coding setups, not the laptop crowd. At 4-bit it weighs about 74.6 GB, which already tells you the story: it does not fit on a 12 GB RTX 3060 or a 24 GB RTX 4090, full stop. You need roughly 96 GB of memory to load it comfortably, so realistically that means a high-memory Apple Silicon machine or a workstation with serious RAM. This is a model you plan your hardware around, not one you casually pull down to try.
In daily use the honest caveat is speed. On an Apple M Max you are looking at around 5 tokens per second, and a CPU-only DDR5 box drops to roughly 1 token per second, which is closer to batch-job territory than interactive chat. It reads and writes code well, but you will feel every reply stream in slowly. The context window is a generous 256K on paper, though memory is the real limit: pushing to 128K context already wants about 132 GB total, so on a 96 GB machine you keep working context modest and lean on shorter, focused prompts.
Against the MoE Qwen 3.5 122B-A10B in related_models, the trade-off is clear: that model activates only a slice of its weights per token and generally feels faster at a similar parameter count, while Devstral 2 runs every one of its 123B parameters on each token. Devstral's standout is being a focused, dense coding specialist from Mistral with a long context, if you have the memory to feed it. One practical note on the license: it ships under a Modified MIT license, so read the specific terms before any commercial deployment rather than assuming plain MIT freedom.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 51.5 GB | 96 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 74.6 GB | 96 GB | Recommended |
| Q5_K_M | 5.65 | 86.9 GB | 128 GB | High |
| Q8_0 | 8.5 | 130.7 GB | 192 GB | Near-original |
| F16 | 16 | 246.0 GB | 256 GB | Original |
Sizes are estimates from parameter count Γ bits per weight; real GGUF builds vary slightly. Β· Data updated: 2026-06-11 Β· How we calculate these numbers β
Memory needed by context length
| Context | KV cache (est.) | Total memory (Q4) |
|---|---|---|
| 4K tokens | ~1.8 GB | ~76.4 GB |
| 8K tokens | ~3.6 GB | ~78.2 GB |
| 32K tokens | ~14.3 GB | ~88.9 GB |
| 128K tokens | ~57.4 GB | ~132.0 GB |
The KV cache grows with context length β a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.
Estimated speed by hardware
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | Won't fit in VRAM |
| NVIDIA RTX 4090 24GB | 1008 GB/s | Won't fit in VRAM |
| Apple M-series (base) | 100 GB/s | ~1 tok/s |
| Apple M-series Pro | 270 GB/s | ~3 tok/s |
| Apple M-series Max | 410 GB/s | ~5 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~1 tok/s |
Token generation is memory-bandwidth bound: tok/s β bandwidth Γ 0.85 Γ· model size at Q4. Real-world numbers vary by runtime and context length.
Run it locally
The easiest path is Ollama β one command and you're chatting:
ollama run devstral-2:123b