fixie-ai · text

ultravox-v0_5-llama-3_2-1b

fixie-ai/ultravox-v0_5-llama-3_2-1b

ultravox-v0_5-llama-3_2-1b at Q4_K_M is exactly 807,694,464 bytes (0.75 GiB / 0.81 GB) — an effective 9.459 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
683M
Architecture
llama
16 layers
Context
native (config.json)
License
mit

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K_M0.75 GiB807,694,4649.459ggml-org
Q8_01.23 GiB1,321,083,00815.471ggml-org

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0961.00 GiB1.00 GiB16 / 0 / 0
8,1922.00 GiB2.00 GiB16 / 0 / 0
16,3844.00 GiB4.00 GiB16 / 0 / 0
32,7688.00 GiB8.00 GiB16 / 0 / 0
65,53616.00 GiB16.00 GiB16 / 0 / 0
131,07232.00 GiB32.00 GiB16 / 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 0.36 GiB. The real file is 0.75 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
16
Attention heads
32
KV heads
32
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 ultravox-v0_5-llama-3_2-1b need?
Q4_K_M is exactly 807,694,464 bytes (0.75 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is ultravox-v0_5-llama-3_2-1b'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 ultravox-v0_5-llama-3_2-1b 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.