UsefulSensors · audio asr

moonshine-streaming-small

UsefulSensors/moonshine-streaming-small

moonshine-streaming-small at Q8_0 is exactly 198,506,848 bytes (0.18 GiB / 0.20 GB) — an effective 11.332 bits per weight, not the nominal 8. Its KV cache at 32K is 0.63 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
140M
Architecture
moonshine_streaming
10 layers
Context
4,096
native (config.json)
License
mit

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q8_00.18 GiB198,506,84811.332handy-computer
F160.26 GiB282,092,12816.104handy-computer
F320.52 GiB562,146,91232.092handy-computer

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.08 GiB0.08 GiB10 / 0 / 0
8,1920.16 GiB0.16 GiB10 / 0 / 0
16,3840.31 GiB0.31 GiB10 / 0 / 0
32,7680.63 GiB0.63 GiB10 / 0 / 0
65,5361.25 GiB1.25 GiB10 / 0 / 0
131,0722.50 GiB2.50 GiB10 / 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 Q8_0 at roughly 0.07 GiB. The real file is 0.18 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
10
Attention heads
8
KV heads
8
Head dim
64
Hidden size
512
Vocab
32,768
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does moonshine-streaming-small need?
Q8_0 is exactly 198,506,848 bytes (0.18 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is moonshine-streaming-small's KV cache?
0.63 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 moonshine-streaming-small 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.