hesamation · text · mixture of experts

Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled

hesamation/Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled

Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled at Q4_K_M is exactly 21,166,759,104 bytes (19.71 GiB / 21.17 GB) — an effective 4.710 bits per weight, not the nominal 4. Its KV cache at 32K is 0.63 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
36.0B
total, not active
Architecture
qwen35moe
40 layers
Context
262,144
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
I1-IQ1_S6.97 GiB7,484,143,6161.665mradermacher
I1-IQ1_M7.67 GiB8,239,210,4961.833mradermacher
I1-IQ2_XXS8.85 GiB9,497,655,2962.113mradermacher
I1-IQ2_XS9.79 GiB10,507,032,5762.338mradermacher
I1-IQ2_S9.92 GiB10,652,481,5362.370mradermacher
I1-IQ2_M10.86 GiB11,659,237,3762.594mradermacher
I1-Q2_K_S11.32 GiB12,152,098,8162.704mradermacher
I1-Q2_K12.05 GiB12,939,595,7762.879mradermacher
I1-IQ3_XXS12.69 GiB13,623,760,8963.032mradermacher
I1-IQ3_XS13.49 GiB14,484,146,1763.223mradermacher
I1-Q3_K_S14.14 GiB15,182,186,4963.378mradermacher
I1-IQ3_S14.20 GiB15,250,425,8563.393mradermacher
I1-IQ3_M14.38 GiB15,440,521,2163.436mradermacher
I1-Q3_K_M15.61 GiB16,764,766,2083.731mradermacher
I1-Q3_K_L16.87 GiB18,115,332,0964.031mradermacher
I1-IQ4_XS17.44 GiB18,728,779,7764.168mradermacher
I1-Q4_018.44 GiB19,799,269,3764.406mradermacher
I1-Q4_K_S18.52 GiB19,889,905,6644.426mradermacher
Q4_K_M19.71 GiB21,166,759,1044.710733hesamation
I1-Q4_K_M19.71 GiB21,166,759,9364.710mradermacher
I1-Q4_120.35 GiB21,848,170,4964.862mradermacher
I1-Q5_K_S22.33 GiB23,981,285,3765.336mradermacher
Q5_K_M23.03 GiB24,729,132,2245.503733hesamation
I1-Q5_K_M23.03 GiB24,729,133,0565.503mradermacher
Q6_K26.56 GiB28,514,153,6646.345733hesamation
I1-Q6_K26.56 GiB28,514,154,4966.345mradermacher
Q8_034.37 GiB36,903,140,5448.212733hesamation
F1666.19 GiB71,065,942,65615.814753mudler

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.08 GiB0.31 GiB4.00×10 / 0 / 30
8,1920.16 GiB0.63 GiB4.00×10 / 0 / 30
16,3840.31 GiB1.25 GiB4.00×10 / 0 / 30
32,7680.63 GiB2.50 GiB4.00×10 / 0 / 30
65,5361.25 GiB5.00 GiB4.00×10 / 0 / 30
131,0722.50 GiB10.00 GiB4.00×10 / 0 / 30

30 of 40 layers use linear attention, which keeps a fixed-size recurrent state instead of a per-token cache. Those layers do not grow with context at all — treating them as ordinary attention, as a flat formula does, overstates this model's cache by roughly 4.0× at long context.

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 18.83 GiB. The real file is 19.71 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
40
Attention heads
16
KV heads
2
Head dim
256
Hidden size
2048
Vocab
248,320
Sliding window
none
SWA period
MLA
no
Experts
256
Experts per token
8
use_sliding_window

Questions people ask

How much VRAM does Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled need?
Q4_K_M is exactly 21,166,759,104 bytes (19.71 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled's KV cache?
0.63 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 Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled a mixture-of-experts model?
Yes — 256 experts, 8 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 Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled 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.