NeverSleep · text · mixture of experts

Noromaid-v0.4-Mixtral-Instruct-8x7b-Zloss

NeverSleep/Noromaid-v0.4-Mixtral-Instruct-8x7b-Zloss

Noromaid-v0.4-Mixtral-Instruct-8x7b-Zloss at Q4_K_M is exactly 28,379,301,792 bytes (26.43 GiB / 28.38 GB) — an effective 4.861 bits per weight, not the nominal 4. Its KV cache at 32K is 4.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
46.7B
total, not active
Architecture
llama
32 layers
Context
32,768
native (config.json)
License
cc-by-nc-4.0

Shipped quantizations

● exact bytes, summed from published files
QuantSize●Exact bytes●Effective bpw●Tensors●Publisher
Q2_K15.99 GiB17,170,761,6322.941—TheBloke
Q2_K16.51 GiB17,728,038,8163.037—mradermacher
IQ3_XS18.35 GiB19,701,139,3603.375—mradermacher
IQ3_S19.42 GiB20,849,330,0803.571—mradermacher
Q3_K_S19.42 GiB20,849,330,0803.571—mradermacher
IQ3_M20.35 GiB21,847,574,4323.742—mradermacher
Q3_K_M20.93 GiB22,477,285,2803.850—TheBloke
Q3_K_M21.39 GiB22,963,259,2963.933—mradermacher
Q3_K_L22.90 GiB24,586,454,9444.212—mradermacher
IQ4_XS24.02 GiB25,790,949,2804.418—mradermacher
Q4_024.63 GiB26,441,533,3444.529—TheBloke
Q4_K_S25.30 GiB27,162,388,3844.653—mradermacher
Q4_K_M26.43 GiB28,379,301,7924.861—TheBloke
Q4_K_M26.88 GiB28,865,275,8084.944—mradermacher
Q5_030.02 GiB32,229,279,6485.521—TheBloke
Q5_K_S30.41 GiB32,648,144,8005.593—mradermacher
Q5_K_M30.95 GiB33,227,524,0005.692—TheBloke
Q5_K_M31.34 GiB33,646,389,1525.763—mradermacher
Q6_K35.74 GiB38,378,760,0966.574—TheBloke
Q6_K36.13 GiB38,797,625,2486.646—mradermacher
Q8_046.22 GiB49,624,262,5608.500—TheBloke

KV cache by context

computed per layer
ContextKV cache (f16)●Flat formulaOverstated byFull / windowed / recurrent
4,0960.50 GiB0.50 GiB—32 / 0 / 0
8,1921.00 GiB1.00 GiB—32 / 0 / 0
16,3842.00 GiB2.00 GiB—32 / 0 / 0
32,7684.00 GiB4.00 GiB—32 / 0 / 0
65,5368.00 GiB8.00 GiB—32 / 0 / 0
131,07216.00 GiB16.00 GiB—32 / 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 24.47 GiB. The real file is 26.43 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

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

Questions people ask

How much VRAM does Noromaid-v0.4-Mixtral-Instruct-8x7b-Zloss need?
Q4_K_M is exactly 28,379,301,792 bytes (26.43 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-v0.4-Mixtral-Instruct-8x7b-Zloss's KV cache?
4.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.
Is Noromaid-v0.4-Mixtral-Instruct-8x7b-Zloss a mixture-of-experts model?
Yes — 8 experts, 2 routed per token. Every expert must be resident, but only the routed ones are read per token, which is why its memory requirement and its speed behave very differently.
Which quantization of Noromaid-v0.4-Mixtral-Instruct-8x7b-Zloss 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.