No — not on this device

Llama 4 Scout 109B-A17B at Q4_K_M needs 63.4 GB against 8.8 GB usable, and the shortfall of 54.6 GB is more than 64 GB of system RAM can cover at a tolerable speed. A smaller sibling or a lower quantisation is the honest answer here.

Does not fit 8K context Q4_K_M · 61.3 GB Llama 4 Community Released 5 Apr 2025 Vision

A 10M-token window on paper, chunked attention in practice (8K chunks on 3 of 4 layers). Needs 64 GB+ at Q4.

What hardware do I need for Llama 4 Scout 109B-A17B? →

Fits instead: Llama 3.1 8B Instruct (6.1 GB) · Llama 3.2 3B Instruct (3.3 GB)

The VRAM budget

weights 61.3 GB
Weights 61.3 GB KV cache @ 8K 1.50 GB Runtime overhead 0.6 GB Over budget 54.6 GB past 8.8 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
Q8_0 107.9 GB 110.0 GB ~0.9 −0.1% ppl 101.2 GB over
Q6_K 83.2 GB 85.3 GB ~1.2 −0.4% ppl 76.5 GB over
Q5_K_M 71.9 GB 74.0 GB ~1.4 −0.8% ppl 65.2 GB over
Q4_K_M 61.3 GB 63.4 GB ~1.6 −1.9% ppl 54.6 GB over
Q3_K_M 49.6 GB 51.7 GB ~2.1 −5.4% ppl 42.9 GB over
Q2_K 42.5 GB 44.6 GB ~2.5 −15% ppl 35.8 GB over

Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it. This model interleaves sliding-window layers (8192 tokens, 12 of 48 layers global), which is why its cache barely grows with context.

How to run it

terminal
$ llama-server \
    -hf meta-llama/Llama-4-Scout-17B-16E-Instruct:Q4_K_M \
    -c 8192 -ngl 5

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

01Download is 61.3 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