KaLM-Embedding · embedding

KaLM-embedding-multilingual-mini-instruct-v2.5

KaLM-Embedding/KaLM-embedding-multilingual-mini-instruct-v2.5

KaLM-embedding-multilingual-mini-instruct-v2.5 at Q8_0 is exactly 531,066,976 bytes (0.49 GiB / 0.53 GB) — an effective 8.600 bits per weight, not the nominal 8.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
494M
Architecture
qwen2
24 layers
Context
131,072
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q8_00.49 GiB531,066,9768.600290Aashraf995

No KV cache

architectural, not a gap in our data

This architecture allocates no KV cache. Encoder and embedding models process their input in one pass rather than generating token by token, so there is nothing to carry forward between steps and memory does not grow with context. Its footprint is the weights plus a working buffer, and that is the whole story.

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

Architecture

from config.json
Layers
24
Attention heads
14
KV heads
2
Head dim
64
Hidden size
896
Vocab
151,936
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window
false

Questions people ask

How much VRAM does KaLM-embedding-multilingual-mini-instruct-v2.5 need?
Q8_0 is exactly 531,066,976 bytes (0.49 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of KaLM-embedding-multilingual-mini-instruct-v2.5 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.