Only with CPU offload

Ling 3.0 Flash 124B-A5B at Q4_K_M needs 70.4 GB but only 62.4 GB is addressable, so about 11% of the layers would stream from system RAM at roughly 60 GB/s. Expect around 33 tokens per second — usable for batch work, painful for chat.

89% on GPU 8K context Q4_K_M · 69.7 GB MIT Released 2 Aug 2026 New this month Not in the Ollama library

A 124B hybrid (5 linear-attention layers per MLA layer) with 5.1B active: SWE-bench Pro 56.6 and AIME 93 claimed. Built for 96–128 GB machines.

What hardware do I need for Ling 3.0 Flash 124B-A5B? →

Fits instead: Ling 3.0 Tiny 7.9B-A1.3B (5.1 GB)

The VRAM budget

weights 69.7 GB
Weights 69.7 GB KV cache @ 8K 0.06 GB Runtime overhead 0.6 GB Over budget 8.0 GB past 62.4 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
Q8_0 122.7 GB 123.4 GB ~5.4 −0.1% ppl 61.0 GB over
Q6_K 94.7 GB 95.4 GB ~9.6 −0.4% ppl 33.0 GB over
Q5_K_M 81.8 GB 82.5 GB ~15 −0.8% ppl 20.1 GB over
Q4_K_M 69.7 GB 70.4 GB ~33 −1.9% ppl 8.0 GB over
Q3_K_M 56.4 GB 57.1 GB 256K 164 −5.4% ppl Long context
Q2_K 48.4 GB 49.0 GB 256K 192 −15% ppl Long context

Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it. Only 7 of its 42 blocks keep a per-token KV cache; the rest are linear-attention, Mamba or convolution blocks with a fixed-size state. This model uses multi-head latent attention, so its cache is a compressed latent rather than full K and V.

How to run it

terminal
$ llama-server \
    -hf inclusionAI/Ling-3.0-flash:Q4_K_M \
    -c 8192 -ngl 37

The engine underneath most of the others. Every knob is exposed. More on llama.cpp.

01Download is 69.7 GB. Keep it on an SSD — a first load off a spinning disk takes minutes.
02Close anything else holding VRAM. A browser with hardware acceleration can sit on 1–2 GB.
03If it falls back to CPU silently, drop the context first, then step down a quantisation.
See all models for this rig Compare with another model