unsloth · text

meta-llama-3.1-8b-bnb-4bit

unsloth/meta-llama-3.1-8b-bnb-4bit

meta-llama-3.1-8b-bnb-4bit at Q4_K_M is exactly 4,920,734,080 bytes (4.58 GiB / 4.92 GB) — an effective 4.772 bits per weight, not the nominal 4. Its KV cache at 32K is 4.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
8.2B
Architecture
llama
32 layers
Context
131,072
native (config.json)
License
creativeml-openrail-m

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q3_K_S3.41 GiB3,664,499,0723.554theprint
Q3_K_M3.74 GiB4,018,917,7603.898theprint
Q4_K_S4.37 GiB4,692,668,8004.551theprint
Q4_K_M4.58 GiB4,920,734,0804.772baoqtrinh
Q4_K_M4.58 GiB4,920,734,0804.772theprint
Q5_K_M5.34 GiB5,732,987,2645.560theprint
Q6_K6.14 GiB6,596,006,2726.397theprint
Q8_07.95 GiB8,540,770,6888.283theprint
F1614.97 GiB16,068,891,00815.584prithivMLmods
F1614.97 GiB16,068,891,00815.584theprint
BF1614.97 GiB16,068,891,00815.584theprint
F1614.97 GiB16,068,891,00815.584baoqtrinh

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.50 GiB0.50 GiB32 / 0 / 0
8,1921.00 GiB1.00 GiB32 / 0 / 0
16,3842.00 GiB2.00 GiB32 / 0 / 0
32,7684.00 GiB4.00 GiB32 / 0 / 0
65,5368.00 GiB8.00 GiB32 / 0 / 0
131,07216.00 GiB16.00 GiB32 / 0 / 0

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 4.32 GiB. The real file is 4.58 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
32
Attention heads
32
KV heads
8
Head dim
128
Hidden size
4096
Vocab
128,256
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does meta-llama-3.1-8b-bnb-4bit need?
Q4_K_M is exactly 4,920,734,080 bytes (4.58 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is meta-llama-3.1-8b-bnb-4bit's KV cache?
4.00 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of meta-llama-3.1-8b-bnb-4bit should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.