Yes, just — 0.9 GB spare

Llama 3.1 8B Instruct at Q4_K_M fits your GeForce RTX 5060 entirely on the GPU at 8K context, at an estimated 60 tokens per second. Past 15K the KV cache pushes it over — quantise the cache to q8_0, or step down a quantisation, to go longer.

Fully on GPU 8K context Q4_K_M · 4.5 GB Llama 3.1 Community Released Jul 2024

Still the most widely deployed local model, with the largest fine-tune ecosystem. Not the strongest 8B any more.

What hardware do I need for Llama 3.1 8B Instruct? →

The VRAM budget

weights 4.5 GB
Weights 4.5 GB KV cache @ 8K 1.00 GB Runtime overhead 0.6 GB Free 0.9 GB of 7.0 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
F16 15.0 GB 16.6 GB ~3.5 Reference 9.6 GB over
Q8_0 7.9 GB 9.5 GB ~11 −0.1% ppl 2.5 GB over
Q6_K 6.1 GB 7.7 GB 2K ~25 −0.4% ppl 0.7 GB over
Q5_K_M 5.3 GB 6.9 GB 8K 51 −0.8% ppl Fits
Q4_K_M 4.5 GB 6.1 GB 15K 60 −1.9% ppl Recommended
Q3_K_M 3.7 GB 5.3 GB 21K 74 −5.4% ppl Long context
Q2_K 3.1 GB 4.7 GB 26K 87 −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.

How to run it

terminal
$ llama-server \
    -hf meta-llama/Llama-3.1-8B-Instruct:Q4_K_M \
    -c 8192 -ngl 99

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

01Download is 4.5 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.
03Only 0.9 GB is spare, so a long system prompt can still push it over. Its real ceiling here is 15K context.
See all models for this rig Compare with another model