How much VRAM does fable-traces need?

Q4_K_M is exactly 2,497,276,608 bytes (2.33 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

How large is fable-traces's KV cache?

4.50 GiB at 32K context with an f16 cache, computed per layer from the model's architecture. Quantizing the cache to q8_0 roughly halves it.

AliesTaha · text

fable-traces

AliesTaha/fable-traces

fable-traces at Q4_K_M is exactly 2,497,276,608 bytes (2.33 GiB / 2.50 GB) — an effective 4.967 bits per weight, not the nominal 4. Its KV cache at 32K is 4.50 GiB.

From the file· summed from 1 file(s)From the file· KV per layer

Parameters

4.0B

Architecture

qwen3

36 layers

Context

262,144

native (config.json)

License

apache-2.0

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
IQ2_M	1.41 GiB	1,512,982,624	3.009	—	liodon-ai
IQ3_M	1.83 GiB	1,962,894,944	3.904	—	liodon-ai
IQ4_XS	2.11 GiB	2,270,750,304	4.516	—	liodon-ai
Q4_K_M	2.33 GiB	2,497,276,608	4.967	—	Anonymouse123
Q4_K_M	2.33 GiB	2,497,279,584	4.967	—	liodon-ai
Q5_K_M	2.69 GiB	2,889,512,544	5.747	—	liodon-ai
Q6_K	3.08 GiB	3,306,260,064	6.576	—	liodon-ai
Q8_0	3.99 GiB	4,280,404,064	8.513	—	liodon-ai

KV cache by context

computed per layer

Context	KV cache (f16)●	Flat formula	Overstated by	Full / windowed / recurrent
4,096	0.56 GiB	0.56 GiB	—	36 / 0 / 0
8,192	1.13 GiB	1.13 GiB	—	36 / 0 / 0
16,384	2.25 GiB	2.25 GiB	—	36 / 0 / 0
32,768	4.50 GiB	4.50 GiB	—	36 / 0 / 0
65,536	9.00 GiB	9.00 GiB	—	36 / 0 / 0
131,072	18.00 GiB	18.00 GiB	—	36 / 0 / 0

Compare with

same modality, comparable size

vs gemma-4-E4B-it vs Qwen3-4B vs Qwen3-8B vs HyperCLOVAX-SEED-Text-Instruct-1.5B vs Llama-3.2-1B-Instruct vs Qwen3-VL-8B-Instruct-abliterated-v1 All alternatives →Will it fit on my card? →

Why other calculators give a different number

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

Architecture

from config.json

Layers

Attention heads

KV heads

Head dim

128

Hidden size

2560

Vocab

151,936

Sliding window

none

SWA period

—

MLA

Experts

—

Experts per token

—

use_sliding_window

false

Questions people ask

How much VRAM does fable-traces need?: Q4_K_M is exactly 2,497,276,608 bytes (2.33 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is fable-traces's KV cache?: 4.50 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 fable-traces 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.