FireRedTeam · text

FireRedPunc

FireRedTeam/FireRedPunc

FireRedPunc at IQ4_XS is exactly 54,707,712 bytes (0.05 GiB / 0.05 GB) — an effective 4.304 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
102M
Architecture
fireredpunc
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
IQ4_XS0.05 GiB54,707,7124.304cstr
Q4_K0.05 GiB57,886,9444.554cstr
Q8_00.10 GiB108,664,8008.550cstr

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 IQ4_XS at roughly 0.05 GiB. The real file is 0.05 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

Architecture unavailable — this repository is gated and no ungated mirror was found. Exact file sizes above are still authoritative; only the KV math needs the config.

Questions people ask

How much VRAM does FireRedPunc need?
IQ4_XS is exactly 54,707,712 bytes (0.05 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of FireRedPunc 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.
FireRedPunc — VRAM requirements, exact quant sizes — ossmodeldb