zai-org · audio asr

GLM-ASR-Nano-2512

zai-org/GLM-ASR-Nano-2512

GLM-ASR-Nano-2512 at Q4_K is exactly 980,472,032 bytes (0.91 GiB / 0.98 GB) — an effective 3.474 bits per weight, not the nominal 4. Its KV cache at 32K is 1.75 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
2.3B
Architecture
glmasr
28 layers
Context
8,192
native (config.json)
License
mit

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K0.91 GiB980,472,0323.474concedo
Q4_K1.23 GiB1,325,316,4484.696cstr
Q8_01.58 GiB1,696,635,1046.011concedo
Q8_02.27 GiB2,436,544,8648.633cstr
BF162.97 GiB3,190,364,38411.304concedo

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.22 GiB0.22 GiB28 / 0 / 0
8,1920.44 GiB0.44 GiB28 / 0 / 0
16,3840.88 GiB0.88 GiB28 / 0 / 0
32,7681.75 GiB1.75 GiB28 / 0 / 0
65,5363.50 GiB3.50 GiB28 / 0 / 0
131,0727.00 GiB7.00 GiB28 / 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 at roughly 1.18 GiB. The real file is 0.91 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
28
Attention heads
16
KV heads
4
Head dim
128
Hidden size
2048
Vocab
59,264
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does GLM-ASR-Nano-2512 need?
Q4_K is exactly 980,472,032 bytes (0.91 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is GLM-ASR-Nano-2512's KV cache?
1.75 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 GLM-ASR-Nano-2512 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.