NeverSleep · text

Noromaid-20b-v0.1.1

NeverSleep/Noromaid-20b-v0.1.1

Noromaid-20b-v0.1.1 at Q4_K_M is exactly 12,042,208,864 bytes (11.22 GiB / 12.04 GB) — an effective 4.818 bits per weight, not the nominal 4. Its KV cache at 32K is 38.75 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
20.0B
Architecture
llama
62 layers
Context
4,096
native (config.json)
License
cc-by-nc-4.0

Shipped quantizations

● exact bytes, summed from published files
QuantSize●Exact bytes●Effective bpw●Tensors●Publisher
I1-IQ1_S4.09 GiB4,393,983,6161.758—mradermacher
I1-IQ1_M4.44 GiB4,767,108,7361.907—mradermacher
I1-IQ2_XXS5.02 GiB5,388,983,9362.156—mradermacher
I1-IQ2_XS5.53 GiB5,937,274,4962.376—mradermacher
I1-IQ2_S5.96 GiB6,397,859,4562.560—mradermacher
I1-IQ2_M6.42 GiB6,895,359,6162.759—mradermacher
I1-Q2_K6.91 GiB7,420,221,0562.969—mradermacher
I1-IQ3_XXS7.07 GiB7,587,788,4163.036—mradermacher
I1-IQ3_XS7.63 GiB8,194,129,5363.279—mradermacher
Q2_K7.74 GiB8,311,592,5443.326—TheBloke
Q3_K_S8.06 GiB8,658,370,1443.464—TheBloke
I1-Q3_K_S8.06 GiB8,658,370,1763.464—mradermacher
I1-IQ3_S8.06 GiB8,658,370,1763.464—mradermacher
I1-IQ3_M8.53 GiB9,155,890,8163.663—mradermacher
Q3_K_M9.03 GiB9,697,156,7043.880—TheBloke
I1-Q3_K_M9.04 GiB9,706,004,0963.884—mradermacher
Q3_K_L9.90 GiB10,627,767,9044.252—TheBloke
I1-Q3_K_L9.90 GiB10,627,767,9364.252—mradermacher
I1-IQ4_XS9.94 GiB10,672,342,6564.270—mradermacher
Q4_010.52 GiB11,292,026,4644.518—TheBloke
I1-Q4_010.55 GiB11,322,992,2564.530—mradermacher
Q4_K_S10.56 GiB11,340,523,1044.537—TheBloke
I1-Q4_K_S10.59 GiB11,367,065,2164.548—mradermacher
Q4_K_M11.22 GiB12,042,208,8644.818—TheBloke
I1-Q4_K_M11.22 GiB12,042,208,8964.818—mradermacher
Q5_012.83 GiB13,770,761,8245.510—TheBloke
Q5_K_S12.83 GiB13,770,761,8245.510—TheBloke
I1-Q5_K_S12.83 GiB13,770,761,8565.510—mradermacher
Q5_K_M13.18 GiB14,157,219,4245.665—TheBloke
I1-Q5_K_M13.18 GiB14,157,219,4565.665—mradermacher
Q6_K15.28 GiB16,404,418,1446.564—TheBloke
I1-Q6_K15.28 GiB16,404,418,1766.564—mradermacher
Q8_019.79 GiB21,246,647,9048.501—TheBloke

KV cache by context

computed per layer
ContextKV cache (f16)●Flat formulaOverstated byFull / windowed / recurrent
4,0964.84 GiB4.84 GiB—62 / 0 / 0
8,1929.69 GiB9.69 GiB—62 / 0 / 0
16,38419.38 GiB19.38 GiB—62 / 0 / 0
32,76838.75 GiB38.75 GiB—62 / 0 / 0
65,53677.50 GiB77.50 GiB—62 / 0 / 0
131,072155.00 GiB155.00 GiB—62 / 0 / 0

Compare with

same modality, comparable size
vs Qwen3-Coder-30B-A3B-Instructvs Qwen3.6-27Bvs Qwen3.8-27Bvs gemma-4-12B-it-qat-q4_0-unquantizedvs gemma-4-E4B-itvs Qwen3-30B-A3B-Thinking-2507All alternatives →Will it fit on my card? →

Will it run on your card?

full quant x context sweep
By VRAM:8GB12GB16GB24GB32GB48GB
Radeon RX 6500 XT 4GBGeForce RTX 3050 6GBGeForce RTX 5050 8GBGeForce RTX 3080 10GBGeForce RTX 2080 Ti 11GBGeForce RTX 5070 12GBGeForce RTX 5060 Ti 16GBApple M3 Pro 18GBGeForce RTX 3080 Ti 20GBGeForce RTX 5090 D V2 24GBGeForce RTX 5090 D 32GBApple M5 Max 36GBApple M5 Pro 48GBApple M5 Max 64GBApple M3 Ultra 96GBApple M5 Max 128GBApple M2 Ultra 192GBApple M3 Ultra 256GBApple M3 Ultra 512GB

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 10.47 GiB. The real file is 11.22 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

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

Questions people ask

How much VRAM does Noromaid-20b-v0.1.1 need?
Q4_K_M is exactly 12,042,208,864 bytes (11.22 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Noromaid-20b-v0.1.1's KV cache?
38.75 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 Noromaid-20b-v0.1.1 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.