ArliAI · text

Mistral-Nemo-12B-ArliAI-RPMax-v1.2

ArliAI/Mistral-Nemo-12B-ArliAI-RPMax-v1.2

Mistral-Nemo-12B-ArliAI-RPMax-v1.2 at F16 is exactly 24,504,279,488 bytes (22.82 GiB / 24.50 GB) — an effective 16.006 bits per weight, not the nominal 1. Its KV cache at 32K is 5.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
12.2B
Architecture
llama
40 layers
Context
1,024,000
native (config.json)
License
unlicense

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
F1622.82 GiB24,504,279,48816.006Lewdiculous
BF1622.82 GiB24,504,279,48816.006Lewdiculous

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.63 GiB0.63 GiB40 / 0 / 0
8,1921.25 GiB1.25 GiB40 / 0 / 0
16,3842.50 GiB2.50 GiB40 / 0 / 0
32,7685.00 GiB5.00 GiB40 / 0 / 0
65,53610.00 GiB10.00 GiB40 / 0 / 0
131,07220.00 GiB20.00 GiB40 / 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 F16 at roughly 6.42 GiB. The real file is 22.82 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
40
Attention heads
32
KV heads
8
Head dim
128
Hidden size
5120
Vocab
131,072
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does Mistral-Nemo-12B-ArliAI-RPMax-v1.2 need?
F16 is exactly 24,504,279,488 bytes (22.82 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Mistral-Nemo-12B-ArliAI-RPMax-v1.2's KV cache?
5.00 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 Mistral-Nemo-12B-ArliAI-RPMax-v1.2 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.