0xSero · text · mixture of experts

Qwen3.5-88B

0xSero/Qwen3.5-88B

Qwen3.5-88B at Q4_K_M is exactly 53,323,531,328 bytes (49.66 GiB / 53.32 GB) — an effective 4.866 bits per weight, not the nominal 4. Its KV cache at 32K is 0.75 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
87.7B
total, not active
Architecture
qwen35moe
48 layers
Context
262,144
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
I1-IQ1_S17.20 GiB18,472,625,6961.686mradermacher
I1-IQ1_M19.01 GiB20,411,635,2321.863mradermacher
I1-IQ2_XXS22.02 GiB23,643,317,7922.157mradermacher
IQ2_XS24.44 GiB26,238,100,5442.394RobinsonLabs
I1-IQ2_XS24.44 GiB26,238,101,0242.394mradermacher
I1-IQ2_S24.71 GiB26,531,526,1762.421mradermacher
IQ2_M27.12 GiB29,116,871,7442.657RobinsonLabs
I1-IQ2_M27.12 GiB29,116,872,2242.657mradermacher
I1-Q2_K_S28.30 GiB30,383,580,7042.772mradermacher
I1-Q2_K30.16 GiB32,389,277,2162.955mradermacher
I1-IQ3_XXS31.82 GiB34,168,567,3283.118mradermacher
IQ3_XS33.82 GiB36,316,054,5923.314RobinsonLabs
I1-IQ3_XS33.82 GiB36,316,055,0723.314mradermacher
I1-Q3_K_S35.47 GiB38,083,905,0563.475mradermacher
I1-IQ3_S35.64 GiB38,266,897,9523.492mradermacher
IQ3_M36.10 GiB38,760,727,6163.537RobinsonLabs
I1-IQ3_M36.10 GiB38,760,728,0963.537mradermacher
Q3_K_M39.26 GiB42,159,735,8723.847RobinsonLabs
I1-Q3_K_M39.26 GiB42,159,736,3523.847mradermacher
I1-Q3_K_L42.43 GiB45,563,020,8324.157mradermacher
IQ4_XS43.89 GiB47,123,129,4084.300RobinsonLabs
I1-IQ4_XS43.89 GiB47,123,129,8884.300mradermacher
I1-Q4_046.41 GiB49,836,418,5924.548mradermacher
Q4_K_S46.63 GiB50,064,286,7844.568RobinsonLabs
I1-Q4_K_S46.63 GiB50,064,287,2644.568mradermacher
Q4_K_M49.66 GiB53,323,531,3284.866RobinsonLabs
I1-Q4_K_M49.66 GiB53,323,531,8084.866mradermacher
I1-Q4_151.27 GiB55,053,018,6565.024mradermacher
I1-Q5_K_S56.33 GiB60,483,135,0085.519mradermacher
Q5_K_M58.10 GiB62,389,519,4245.693RobinsonLabs
I1-Q5_K_M58.10 GiB62,389,519,9045.693mradermacher
Q6_K67.08 GiB72,022,131,7766.572RobinsonLabs
I1-Q6_K67.08 GiB72,022,132,2566.572mradermacher

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.09 GiB0.38 GiB4.00×12 / 0 / 36
8,1920.19 GiB0.75 GiB4.00×12 / 0 / 36
16,3840.38 GiB1.50 GiB4.00×12 / 0 / 36
32,7680.75 GiB3.00 GiB4.00×12 / 0 / 36
65,5361.50 GiB6.00 GiB4.00×12 / 0 / 36
131,0723.00 GiB12.00 GiB4.00×12 / 0 / 36

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

Architecture

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

Questions people ask

How much VRAM does Qwen3.5-88B need?
Q4_K_M is exactly 53,323,531,328 bytes (49.66 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.5-88B's KV cache?
0.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.
Is Qwen3.5-88B a mixture-of-experts model?
Yes — 180 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.5-88B 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.