UsefulSensors · audio asr

moonshine-streaming-tiny

UsefulSensors/moonshine-streaming-tiny

moonshine-streaming-tiny at Q4_K is exactly 32,052,896 bytes (0.03 GiB / 0.03 GB) — an effective 5.821 bits per weight, not the nominal 4. Its KV cache at 32K is 0.23 GiB.

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

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K0.03 GiB32,052,8965.821cstr
Q8_00.05 GiB50,462,8169.164handy-computer
F160.08 GiB89,784,41616.304handy-computer
F320.17 GiB177,817,69632.290handy-computer

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.03 GiB0.03 GiB6 / 0 / 0
8,1920.06 GiB0.06 GiB6 / 0 / 0
16,3840.12 GiB0.12 GiB6 / 0 / 0
32,7680.23 GiB0.23 GiB6 / 0 / 0
65,5360.47 GiB0.47 GiB6 / 0 / 0
131,0720.94 GiB0.94 GiB6 / 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 0.02 GiB. The real file is 0.03 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
6
Attention heads
8
KV heads
8
Head dim
40
Hidden size
320
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-tiny need?
Q4_K is exactly 32,052,896 bytes (0.03 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-tiny's KV cache?
0.23 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-tiny 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.