fableforge-ai · text

NEXUS-Legal

fableforge-ai/NEXUS-Legal

NEXUS-Legal at Q4_K_M is exactly 986,045,472 bytes (0.92 GiB / 0.99 GB) — an effective 5.110 bits per weight, not the nominal 4. Its KV cache at 32K is 0.88 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
1.5B
Architecture
qwen2
28 layers
Context
32,768
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_00.37 GiB395,215,9042.048King3Djbl
IQ1_S0.41 GiB436,524,6722.262King3Djbl
IQ2_XXS0.48 GiB511,014,4322.648King3Djbl
IQ2_XS0.51 GiB550,323,8082.852King3Djbl
IQ2_S0.53 GiB563,806,8162.922King3Djbl
IQ3_XXS0.58 GiB622,361,2483.225King3Djbl
Q2_K0.63 GiB676,301,8563.505King3Djbl
IQ3_XS0.68 GiB731,696,2243.792King3Djbl
Q3_K_S0.71 GiB760,941,4083.943King3Djbl
IQ3_S0.71 GiB762,403,9363.951King3Djbl
IQ3_M0.72 GiB776,661,0884.025King3Djbl
Q3_K_M0.77 GiB824,175,6484.271King3Djbl
Q3_K_L0.82 GiB880,159,5844.561King3Djbl
IQ4_XS0.83 GiB895,728,6724.642King3Djbl
IQ4_NL0.87 GiB936,328,2884.852King3Djbl
Q4_K_S0.88 GiB940,309,3444.873King3Djbl
Q4_K_M0.92 GiB986,045,4725.110King3Djbl
Q4_10.95 GiB1,016,839,0085.270King3Djbl
Q5_K_S1.02 GiB1,098,726,2405.694King3Djbl
Q5_K_M1.05 GiB1,125,047,3285.830King3Djbl
Q6_K1.19 GiB1,272,736,8006.596King3Djbl
Q8_01.53 GiB1,646,570,0168.533King3Djbl
F162.88 GiB3,093,666,14416.032King3Djbl

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.11 GiB0.11 GiB28 / 0 / 0
8,1920.22 GiB0.22 GiB28 / 0 / 0
16,3840.44 GiB0.44 GiB28 / 0 / 0
32,7680.88 GiB0.88 GiB28 / 0 / 0
65,5361.75 GiB1.75 GiB28 / 0 / 0
131,0723.50 GiB3.50 GiB28 / 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_M at roughly 0.81 GiB. The real file is 0.92 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
28
Attention heads
12
KV heads
2
Head dim
128
Hidden size
1536
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 NEXUS-Legal need?
Q4_K_M is exactly 986,045,472 bytes (0.92 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is NEXUS-Legal's KV cache?
0.88 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 NEXUS-Legal 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.
NEXUS-Legal — VRAM requirements, exact quant sizes — ossmodeldb