How much VRAM does NEXUS-Coder-OBLITERATED need?

Q4_K_M is exactly 986,048,800 bytes (0.92 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

How large is NEXUS-Coder-OBLITERATED's KV cache?

0.88 GiB at 32K context with an f16 cache, computed per layer from the model's architecture. Quantizing the cache to q8_0 roughly halves it.

Ngixdev · text

NEXUS-Coder-OBLITERATED

Ngixdev/NEXUS-Coder-OBLITERATED

NEXUS-Coder-OBLITERATED at Q4_K_M is exactly 986,048,800 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

—

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
I1-IQ1_S	0.41 GiB	436,528,192	2.262	—	mradermacher
I1-IQ1_M	0.43 GiB	464,461,888	2.407	—	mradermacher
I1-IQ2_XXS	0.48 GiB	511,018,048	2.648	—	mradermacher
I1-IQ2_XS	0.51 GiB	550,327,360	2.852	—	mradermacher
I1-IQ2_S	0.53 GiB	563,810,368	2.922	—	mradermacher
I1-IQ2_M	0.56 GiB	601,055,296	3.115	—	mradermacher
I1-Q2_K_S	0.60 GiB	640,135,744	3.317	—	mradermacher
I1-IQ3_XXS	0.62 GiB	668,792,896	3.466	—	mradermacher
Q2_K	0.63 GiB	676,305,184	3.505	—	mradermacher
I1-Q2_K	0.63 GiB	676,305,472	3.505	—	mradermacher
I1-IQ3_XS	0.68 GiB	731,699,776	3.792	—	mradermacher
Q3_K_S	0.71 GiB	760,944,928	3.943	—	mradermacher
I1-Q3_K_S	0.71 GiB	760,945,216	3.943	—	mradermacher
I1-IQ3_S	0.71 GiB	762,407,488	3.951	—	mradermacher
I1-IQ3_M	0.72 GiB	776,664,640	4.025	—	mradermacher
Q3_K_M	0.77 GiB	824,178,976	4.271	—	mradermacher
I1-Q3_K_M	0.77 GiB	824,179,264	4.271	—	mradermacher
Q3_K_L	0.82 GiB	880,163,104	4.561	—	mradermacher
I1-Q3_K_L	0.82 GiB	880,163,392	4.561	—	mradermacher
I1-IQ4_XS	0.83 GiB	895,732,288	4.642	—	mradermacher
IQ4_XS	0.84 GiB	902,183,200	4.675	—	mradermacher
I1-IQ4_NL	0.87 GiB	936,331,840	4.852	—	mradermacher
I1-Q4_0	0.87 GiB	937,536,064	4.859	—	mradermacher
Q4_K_S	0.88 GiB	940,312,864	4.873	—	mradermacher
I1-Q4_K_S	0.88 GiB	940,313,152	4.873	—	mradermacher
Q4_K_M	0.92 GiB	986,048,800	5.110	—	mradermacher
I1-Q4_K_M	0.92 GiB	986,049,088	5.110	—	mradermacher
I1-Q4_1	0.95 GiB	1,016,842,816	5.270	—	mradermacher
Q5_K_S	1.02 GiB	1,098,729,760	5.694	—	mradermacher
I1-Q5_K_S	1.02 GiB	1,098,730,048	5.694	—	mradermacher
Q5_K_M	1.05 GiB	1,125,050,656	5.830	—	mradermacher
I1-Q5_K_M	1.05 GiB	1,125,050,944	5.830	—	mradermacher
Q6_K	1.19 GiB	1,272,740,128	6.596	—	mradermacher
I1-Q6_K	1.19 GiB	1,272,740,416	6.596	—	mradermacher
Q8_0	1.53 GiB	1,646,573,344	8.533	—	mradermacher
F16	2.88 GiB	3,093,669,664	16.032	—	mradermacher

KV cache by context

computed per layer

Context	KV cache (f16)●	Flat formula	Overstated by	Full / windowed / recurrent
4,096	0.11 GiB	0.11 GiB	—	28 / 0 / 0
8,192	0.22 GiB	0.22 GiB	—	28 / 0 / 0
16,384	0.44 GiB	0.44 GiB	—	28 / 0 / 0
32,768	0.88 GiB	0.88 GiB	—	28 / 0 / 0
65,536	1.75 GiB	1.75 GiB	—	28 / 0 / 0
131,072	3.50 GiB	3.50 GiB	—	28 / 0 / 0

Compare with

same modality, comparable size

vs Qwen3-4B vs Llama-3.2-1B-Instruct vs ced-base vs gemma-3-1b-it vs Qwen3-1.7B vs embeddinggemma-300m All alternatives →Will it fit on my card? →

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

Attention heads

KV heads

Head dim

128

Hidden size

1536

Vocab

151,936

Sliding window

none

SWA period

—

MLA

Experts

—

Experts per token

—

use_sliding_window

false

Questions people ask

How much VRAM does NEXUS-Coder-OBLITERATED need?: Q4_K_M is exactly 986,048,800 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-Coder-OBLITERATED'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-Coder-OBLITERATED 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.