Jackrong · text

Qwen3.5-9B-DeepSeek-V4-Flash

Jackrong/Qwen3.5-9B-DeepSeek-V4-Flash

Qwen3.5-9B-DeepSeek-V4-Flash at Q4_K_M is exactly 5,629,106,432 bytes (5.24 GiB / 5.63 GB) — an effective 4.665 bits per weight, not the nominal 4. Its KV cache at 32K is 1.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
9.7B
Architecture
qwen35
32 layers
Context
262,144
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
I1-IQ1_S2.55 GiB2,742,639,1362.273mradermacher
I1-IQ1_M2.68 GiB2,877,266,4642.385mradermacher
I1-IQ2_XXS2.89 GiB3,101,645,3442.571mradermacher
I1-IQ2_XS3.06 GiB3,285,342,7522.723mradermacher
I1-IQ2_S3.19 GiB3,427,965,4722.841mradermacher
I1-IQ2_M3.36 GiB3,607,468,5762.990mradermacher
I1-Q2_K_S3.44 GiB3,697,236,5123.064mradermacher
Q2_K3.56 GiB3,827,259,6483.172mradermacher
I1-Q2_K3.56 GiB3,827,259,9363.172mradermacher
I1-IQ3_XXS3.67 GiB3,938,163,2323.264mradermacher
I1-IQ3_XS3.95 GiB4,243,413,5363.517mradermacher
Q3_K_S3.97 GiB4,259,404,0323.530mradermacher
I1-Q3_K_S3.97 GiB4,259,404,3203.530mradermacher
I1-IQ3_S4.07 GiB4,370,815,5203.622mradermacher
I1-IQ3_M4.11 GiB4,415,380,0003.659mradermacher
Q3_K_M4.31 GiB4,623,522,0483.832mradermacher
I1-Q3_K_M4.31 GiB4,623,522,3363.832mradermacher
Q3_K_M4.41 GiB4,737,606,4003.926Jackrong
Q3_K_L4.59 GiB4,925,511,9364.082mradermacher
I1-Q3_K_L4.59 GiB4,925,512,2244.082mradermacher
I1-IQ4_XS4.84 GiB5,196,438,0484.306mradermacher
IQ4_XS4.87 GiB5,227,895,0404.333mradermacher
I1-Q4_04.96 GiB5,325,937,1844.414mradermacher
Q4_K_S4.98 GiB5,351,627,0084.435mradermacher
I1-Q4_K_S4.98 GiB5,351,627,2964.435mradermacher
I1-IQ4_NL5.05 GiB5,418,211,8724.490mradermacher
Q4_K_M5.24 GiB5,629,106,4324.665mradermacher
I1-Q4_K_M5.24 GiB5,629,106,7204.665mradermacher
Q4_K_M5.38 GiB5,780,087,5524.790Jackrong
I1-Q4_15.41 GiB5,809,330,7204.814mradermacher
Q5_K_S5.87 GiB6,305,306,8805.226mradermacher
I1-Q5_K_S5.87 GiB6,305,307,1685.226mradermacher
Q5_K_M6.02 GiB6,467,967,2325.360mradermacher
I1-Q5_K_M6.02 GiB6,467,967,5205.360mradermacher
Q5_K_M6.19 GiB6,642,541,3125.505Jackrong
Q6_K6.85 GiB7,359,256,8326.099mradermacher
I1-Q6_K6.85 GiB7,359,257,1206.099mradermacher
Q6_K7.04 GiB7,558,898,4326.264Jackrong
Q8_08.87 GiB9,527,499,0087.896mradermacher
Q8_09.11 GiB9,786,057,4728.110Jackrong

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.13 GiB0.50 GiB4.00×8 / 0 / 24
8,1920.25 GiB1.00 GiB4.00×8 / 0 / 24
16,3840.50 GiB2.00 GiB4.00×8 / 0 / 24
32,7681.00 GiB4.00 GiB4.00×8 / 0 / 24
65,5362.00 GiB8.00 GiB4.00×8 / 0 / 24
131,0724.00 GiB16.00 GiB4.00×8 / 0 / 24

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

Architecture

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

Questions people ask

How much VRAM does Qwen3.5-9B-DeepSeek-V4-Flash need?
Q4_K_M is exactly 5,629,106,432 bytes (5.24 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-9B-DeepSeek-V4-Flash's KV cache?
1.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.
Which quantization of Qwen3.5-9B-DeepSeek-V4-Flash 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.