huihui-ai · text

Huihui-ThinkingCap-Qwen3.6-27B-abliterated

huihui-ai/Huihui-ThinkingCap-Qwen3.6-27B-abliterated

Huihui-ThinkingCap-Qwen3.6-27B-abliterated at Q4_K_M is exactly 16,810,714,176 bytes (15.66 GiB / 16.81 GB) — an effective 4.916 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.4B
Architecture
qwen35
64 layers
Context
262,144
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K10.12 GiB10,864,591,9363.177mradermacher
I1-Q2_K10.12 GiB10,864,592,2243.177mradermacher
Q3_K_S11.41 GiB12,256,535,6163.584mradermacher
I1-Q3_K_S11.41 GiB12,256,535,9043.584mradermacher
I1-IQ3_S11.74 GiB12,602,606,9443.685mradermacher
I1-IQ3_M11.89 GiB12,768,331,1043.734mradermacher
Q3_K_M12.57 GiB13,500,736,5763.948866mradermacher
I1-Q3_K_M12.57 GiB13,500,736,8643.948mradermacher
Q3_K_L13.56 GiB14,559,798,3364.258mradermacher
I1-Q3_K_L13.56 GiB14,559,798,6244.258mradermacher
I1-IQ4_XS14.26 GiB15,309,038,9444.477mradermacher
IQ4_XS14.36 GiB15,420,449,8564.509866mradermacher
I1-Q4_014.68 GiB15,760,418,1444.609mradermacher
Q4_K_S14.74 GiB15,825,298,4964.628mradermacher
I1-Q4_K_S14.74 GiB15,825,298,7844.628mradermacher
Q4_K_M15.66 GiB16,810,714,1764.916866mradermacher
I1-Q4_K_M15.66 GiB16,810,714,4644.916mradermacher
I1-Q4_116.15 GiB17,343,767,9045.072mradermacher
Q5_K_S17.67 GiB18,971,681,8565.548mradermacher
I1-Q5_K_S17.67 GiB18,971,682,1445.548mradermacher
Q5_K_M18.19 GiB19,535,701,0565.713866mradermacher
I1-Q5_K_M18.19 GiB19,535,701,3445.713mradermacher
Q6_K20.89 GiB22,430,999,6166.560866mradermacher
I1-Q6_K20.89 GiB22,430,999,9046.560mradermacher
Q8_027.05 GiB29,047,084,0968.494866mradermacher

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.25 GiB1.00 GiB4.00×16 / 0 / 48
8,1920.50 GiB2.00 GiB4.00×16 / 0 / 48
16,3841.00 GiB4.00 GiB4.00×16 / 0 / 48
32,7682.00 GiB8.00 GiB4.00×16 / 0 / 48
65,5364.00 GiB16.00 GiB4.00×16 / 0 / 48
131,0728.00 GiB32.00 GiB4.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

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

Architecture

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

Questions people ask

How much VRAM does Huihui-ThinkingCap-Qwen3.6-27B-abliterated need?
Q4_K_M is exactly 16,810,714,176 bytes (15.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 Huihui-ThinkingCap-Qwen3.6-27B-abliterated'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 Huihui-ThinkingCap-Qwen3.6-27B-abliterated 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.