nkpz · text

llama2-22b-chat-wizard-uncensored

nkpz/llama2-22b-chat-wizard-uncensored

llama2-22b-chat-wizard-uncensored at Q2_K is exactly 8,114,369,824 bytes (7.56 GiB / 8.11 GB) — an effective 2.974 bits per weight, not the nominal 2. Its KV cache at 32K is 32.50 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
21.8B
Architecture
llama
40 layers
Context
2,048
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K7.56 GiB8,114,369,8242.974tensorblock
Q3_K_M9.88 GiB10,610,329,8883.889tensorblock

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0964.06 GiB4.06 GiB40 / 0 / 0
8,1928.13 GiB8.13 GiB40 / 0 / 0
16,38416.25 GiB16.25 GiB40 / 0 / 0
32,76832.50 GiB32.50 GiB40 / 0 / 0
65,53665.00 GiB65.00 GiB40 / 0 / 0
131,072130.00 GiB130.00 GiB40 / 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 Q2_K at roughly 11.43 GiB. The real file is 7.56 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
40
Attention heads
52
KV heads
52
Head dim
128
Hidden size
6656
Vocab
32,000
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does llama2-22b-chat-wizard-uncensored need?
Q2_K is exactly 8,114,369,824 bytes (7.56 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is llama2-22b-chat-wizard-uncensored's KV cache?
32.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 llama2-22b-chat-wizard-uncensored 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.