ai-sage · audio asr

GigaAM-v3

ai-sage/GigaAM-v3

GigaAM-v3 at Q4_K_M is exactly 182,497,888 bytes (0.17 GiB / 0.18 GB) — an effective 6.561 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
223M
Architecture
gigaam
null layers
Context
native (config.json)
License
mit

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K_M0.17 GiB182,497,8886.561handy-computer
Q4_K_M0.17 GiB183,246,7526.588560handy-computer
Q4_K_M0.17 GiB183,948,7046.613560handy-computer
Q5_K_M0.19 GiB204,911,2007.367handy-computer
Q5_K_M0.19 GiB205,690,7847.395handy-computer
Q5_K_M0.19 GiB206,392,7367.420560handy-computer
Q6_K0.21 GiB226,439,7768.141552handy-computer
Q6_K0.21 GiB227,252,0008.170560handy-computer
Q6_K0.21 GiB227,953,9528.195560handy-computer
Q8_00.25 GiB272,151,1369.784552handy-computer
Q8_00.25 GiB273,022,8809.816handy-computer
Q8_00.25 GiB273,724,8329.841560handy-computer
F160.42 GiB449,098,33616.146552handy-computer
F160.42 GiB451,084,83216.217handy-computer
F160.42 GiB452,381,40816.264560handy-computer
F320.82 GiB883,603,55231.767handy-computer
F320.83 GiB887,573,53631.910handy-computer
F320.83 GiB890,138,59232.002handy-computer

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.12 GiB. The real file is 0.17 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
Hidden size
Vocab
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does GigaAM-v3 need?
Q4_K_M is exactly 182,497,888 bytes (0.17 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of GigaAM-v3 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.