fdtn-ai · text

antares-1b

fdtn-ai/antares-1b

antares-1b at Q4_K_M is exactly 1,139,251,136 bytes (1.06 GiB / 1.14 GB) — an effective 4.961 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
1.8B
Architecture
granite
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K0.72 GiB769,136,5763.349DevQuasar
Q3_K_M0.88 GiB948,672,4484.131DevQuasar
Q4_K_M1.06 GiB1,139,251,1364.961DevQuasar
Q5_K_M1.23 GiB1,319,606,2085.746DevQuasar
Q6_K1.41 GiB1,511,233,4726.580DevQuasar
Q8_01.82 GiB1,956,150,8808.518AXONVERTEX-AI-RESEARCH
Q8_01.82 GiB1,956,150,8808.518mitkox
Q8_01.82 GiB1,956,157,3768.518DevQuasar

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.96 GiB. The real file is 1.06 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 antares-1b need?
Q4_K_M is exactly 1,139,251,136 bytes (1.06 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of antares-1b 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.