How much VRAM does Qwopus3.6-27B-Coder need?

Q4_K_M is exactly 16,547,399,136 bytes (15.41 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

How large is Qwopus3.6-27B-Coder's KV cache?

2.00 GiB at 32K context with an f16 cache, computed per layer from the model's architecture. Quantizing the cache to q8_0 roughly halves it.

Jackrong · vision language

Qwopus3.6-27B-Coder

Jackrong/Qwopus3.6-27B-Coder

Qwopus3.6-27B-Coder at Q4_K_M is exactly 16,547,399,136 bytes (15.41 GiB / 16.55 GB) — an effective 4.765 bits per weight, not the nominal 4. Its KV cache at 32K is 2.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer

Parameters

27.8B

Architecture

clip

64 layers

Context

262,144

native (config.json)

License

apache-2.0

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
IQ2_XS	8.89 GiB	9,541,911,072	2.748	—	pearsonkyle
IQ2_M	9.74 GiB	10,455,912,992	3.011	—	pearsonkyle
IQ3_M	12.14 GiB	13,032,191,264	3.753	—	pearsonkyle
Q3_K_M	12.39 GiB	13,301,442,016	3.830	—	8sp4rk
Q3_K_M	12.57 GiB	13,500,732,512	3.888	866	Jackrong
IQ4_XS	14.47 GiB	15,533,823,264	4.473	866	pearsonkyle
Q4_K_M	15.41 GiB	16,547,399,136	4.765	—	8sp4rk
Q4_K_M	15.66 GiB	16,810,710,112	4.841	866	Jackrong
Q5_K_M	17.91 GiB	19,231,098,336	5.538	—	8sp4rk
Q5_K_M	18.19 GiB	19,535,696,992	5.625	866	Jackrong
Q6_K	20.57 GiB	22,082,528,736	6.359	—	8sp4rk
Q6_K	20.89 GiB	22,430,995,552	6.459	866	Jackrong
Q8_0	26.63 GiB	28,595,762,656	8.235	—	8sp4rk
Q8_0	27.05 GiB	29,047,080,032	8.364	866	Jackrong

KV cache by context

computed per layer

Context	KV cache (f16)●	Flat formula	Overstated by	Full / windowed / recurrent
4,096	0.25 GiB	1.00 GiB	4.00×	16 / 0 / 48
8,192	0.50 GiB	2.00 GiB	4.00×	16 / 0 / 48
16,384	1.00 GiB	4.00 GiB	4.00×	16 / 0 / 48
32,768	2.00 GiB	8.00 GiB	4.00×	16 / 0 / 48
65,536	4.00 GiB	16.00 GiB	4.00×	16 / 0 / 48
131,072	8.00 GiB	32.00 GiB	4.00×	16 / 0 / 48

48 of 64 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

vs Qwen3.6-35B-A3B vs Qwen3.6-27B-Fable-Fusion-711-Uncensored-Heretic-NM-DAU-MTP vs Qwen3.5-9B vs gemma-4-26B-A4B-it vs gemma-4-12B-it vs Qwen3.5-4B All alternatives →Will it fit on my card? →

Why other calculators give a different number

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

Architecture

from config.json

Layers

Attention heads

KV heads

Head dim

256

Hidden size

5120

Vocab

248,320

Sliding window

none

SWA period

—

MLA

Experts

—

Experts per token

—

use_sliding_window

—

Questions people ask

How much VRAM does Qwopus3.6-27B-Coder need?: Q4_K_M is exactly 16,547,399,136 bytes (15.41 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Qwopus3.6-27B-Coder's KV cache?: 2.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 Qwopus3.6-27B-Coder 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.