← All modelsMODEL CHECK

Can I run Mellum 2 12B-A2.5B?

Mellum 2 12B-A2.5B by JetBrains needs around 12 GB of RAM at the recommended 4-bit quantization (7.3 GB download). Your hardware is checked below β€” instantly, nothing leaves your browser. Expect roughly ~202 tok/s on a NVIDIA RTX 3060 12GB.

Reading your hardware signals…

Real-world notes

Mellum 2 is JetBrains' coding-focused model, built as a mixture-of-experts: 12B parameters total but only about 2.5B active per token. That's the whole point of the design. You get the speed of a roughly 2-3B model, but you still hold the full 12B in memory, so don't be fooled by the active count. At a 4-bit quant it lands around 7.3 GB, with a practical floor of about 12 GB RAM. That fits a 12 GB card like an RTX 3060 or unified memory on an Apple Silicon Mac, but 8 GB is too tight. If you live in JetBrains IDEs and want local code completion, it's aimed squarely at you.

In daily use the MoE design pays off: it feels much faster than its size suggests. On an RTX 3060 12GB you can expect around 202 tokens per second at 4-bit, and an RTX 4090 pushes past 565 β€” well into the range where completions land before you've finished typing the next line. The 128K context is genuinely large for a coding model, handy for feeding it whole files or a repo's worth of headers, but it isn't free. Fill it all the way and total memory climbs to roughly 27.4 GB, far past what a single 12 GB card holds, so keep working context modest unless you have a 24 GB GPU or generous unified memory.

It's worth being clear about scope: this is a coding specialist, not a general assistant. For chat, reasoning, or anything with images, a broader 12B like Gemma 4 12B generally serves you better, and Mistral Nemo 12B tends to be the friendlier pick for open-ended conversation. Mellum 2's standout trait is that MoE speed-to-size ratio on completion-style work, paired with first-class IDE integration from the people who make your editor. And the license is the easy part: Apache 2.0, so you can use it commercially and in production without legal worries. If your main job is code and you have a 12 GB card, it's a strong, fast local choice.

Specifications

Parameters12B (2.5B active)
Context window128K tokens
ProviderJetBrains
LicenseApache 2.0
Released2026-06
Best forCoding

Size by quantization

QuantizationBits/weightDownloadMin RAMQuality
Q2_K3.355.0 GB8 GBNoticeable loss
Q4_K_MRecommended4.857.3 GB12 GBRecommended
Q5_K_M5.658.5 GB16 GBHigh
Q8_08.512.8 GB24 GBNear-original
F161624.0 GB32 GBOriginal

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

ContextKV cache (est.)Total memory (Q4)
4K tokens~0.6 GB~7.9 GB
8K tokens~1.3 GB~8.6 GB
32K tokens~5.0 GB~12.3 GB
128K tokens~20.1 GB~27.4 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

HardwareBandwidth~Speed
NVIDIA RTX 3060 12GB360 GB/s~202 tok/s
NVIDIA RTX 4090 24GB1008 GB/s~565 tok/s
Apple M-series (base)100 GB/s~56 tok/s
Apple M-series Pro270 GB/s~151 tok/s
Apple M-series Max410 GB/s~230 tok/s
CPU only (dual-channel DDR5)60 GB/s~34 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.

Frequently asked questions

Mellum 2 12B-A2.5B System Requirements β€” Can I Run It Locally?