How much VRAM does Caller need?

Q4_K_M is exactly 19,851,339,296 bytes (18.49 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

How large is Caller's KV cache?

8.00 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.

arcee-ai · text

Caller

arcee-ai/Caller

Caller at Q4_K_M is exactly 19,851,339,296 bytes (18.49 GiB / 19.85 GB) — an effective 4.847 bits per weight, not the nominal 4. Its KV cache at 32K is 8.00 GiB.

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

Parameters

32.8B

Architecture

qwen2

64 layers

Context

32,768

native (config.json)

License

apache-2.0

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
IQ2_XXS	8.41 GiB	9,028,253,216	2.204	—	bartowski
IQ2_XS	9.27 GiB	9,957,553,696	2.431	—	bartowski
IQ2_S	9.67 GiB	10,387,572,256	2.536	—	bartowski
IQ2_M	10.49 GiB	11,264,443,936	2.751	—	bartowski
Q2_K	11.47 GiB	12,313,101,856	3.006	—	bartowski
IQ3_XXS	11.96 GiB	12,839,274,016	3.135	—	bartowski
Q2_K_L	12.18 GiB	13,073,421,856	3.192	—	bartowski
IQ3_XS	12.76 GiB	13,705,516,576	3.346	—	bartowski
Q3_K_S	13.40 GiB	14,392,333,856	3.514	—	bartowski
IQ3_M	13.79 GiB	14,810,125,856	3.616	—	bartowski
Q3_K_M	14.84 GiB	15,935,051,296	3.891	—	bartowski
Q3_K_L	16.06 GiB	17,247,082,016	4.211	—	bartowski
IQ4_XS	16.48 GiB	17,693,156,896	4.320	—	bartowski
IQ4_NL	17.40 GiB	18,682,177,056	4.562	—	bartowski
Q4_0	17.43 GiB	18,711,012,896	4.569	—	bartowski
Q4_K_S	17.49 GiB	18,784,413,216	4.587	—	bartowski
Q4_K_M	18.49 GiB	19,851,339,296	4.847	—	bartowski
Q4_K_L	19.03 GiB	20,429,182,496	4.988	—	bartowski
Q4_1	19.22 GiB	20,639,245,856	5.040	—	bartowski
Q5_K_S	21.08 GiB	22,638,257,696	5.528	—	bartowski
Q5_K_M	21.66 GiB	23,262,160,416	5.680	—	bartowski
Q5_K_L	22.11 GiB	23,742,682,656	5.797	—	bartowski
Q6_K	25.04 GiB	26,886,157,856	6.565	—	bartowski
Q6_K_L	25.39 GiB	27,263,276,576	6.657	—	bartowski
Q8_0	32.43 GiB	34,820,888,096	8.502	—	bartowski
BF162 shards	61.04 GiB	65,535,972,832	16.002	—	bartowski

KV cache by context

computed per layer

Context	KV cache (f16)●	Flat formula	Overstated by	Full / windowed / recurrent
4,096	1.00 GiB	1.00 GiB	—	64 / 0 / 0
8,192	2.00 GiB	2.00 GiB	—	64 / 0 / 0
16,384	4.00 GiB	4.00 GiB	—	64 / 0 / 0
32,768	8.00 GiB	8.00 GiB	—	64 / 0 / 0
65,536	16.00 GiB	16.00 GiB	—	64 / 0 / 0
131,072	32.00 GiB	32.00 GiB	—	64 / 0 / 0

Compare with

same modality, comparable size

vs Qwen3-Coder-30B-A3B-Instruct vs Qwen3.6-27B vs Qwen3.8-27B vs gemma-4-12B-it-qat-q4_0-unquantized vs gemma-4-E4B-it vs Qwen3-30B-A3B-Thinking-2507 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 17.16 GiB. The real file is 18.49 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

5120

Vocab

152,064

Sliding window

none

SWA period

—

MLA

Experts

—

Experts per token

—

use_sliding_window

false

Questions people ask

How much VRAM does Caller need?: Q4_K_M is exactly 19,851,339,296 bytes (18.49 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Caller's KV cache?: 8.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 Caller 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.