nicoboss · text

Baichuan-M2-32B-abliterated

nicoboss/Baichuan-M2-32B-abliterated

Baichuan-M2-32B-abliterated at Q4_K_M is exactly 19,851,337,920 bytes (18.49 GiB / 19.85 GB) — an effective 4.847 bits per weight, not the nominal 4. Its KV cache at 32K is 8.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
32.8B
Architecture
qwen2
64 layers
Context
131,072
native (config.json)
License

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K11.47 GiB12,313,100,4803.006mradermacher
Q3_K_S13.40 GiB14,392,332,4803.514mradermacher
Q3_K_M14.84 GiB15,935,049,9203.891mradermacher
Q3_K_L16.06 GiB17,247,080,6404.211mradermacher
IQ4_XS16.64 GiB17,870,102,7204.363mradermacher
Q4_K_S17.49 GiB18,784,411,8404.587mradermacher
Q4_K_M18.49 GiB19,851,337,9204.847mradermacher
Q5_K_S21.08 GiB22,638,256,3205.528mradermacher
Q5_K_M21.66 GiB23,262,159,0405.680mradermacher
Q6_K25.04 GiB26,886,156,4806.565mradermacher
Q8_032.43 GiB34,820,886,7208.502mradermacher

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0961.00 GiB1.00 GiB64 / 0 / 0
8,1922.00 GiB2.00 GiB64 / 0 / 0
16,3844.00 GiB4.00 GiB64 / 0 / 0
32,7688.00 GiB8.00 GiB64 / 0 / 0
65,53616.00 GiB16.00 GiB64 / 0 / 0
131,07232.00 GiB32.00 GiB64 / 0 / 0

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

Architecture

from config.json
Layers
64
Attention heads
40
KV heads
8
Head dim
128
Hidden size
5120
Vocab
152,064
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window
false

Questions people ask

How much VRAM does Baichuan-M2-32B-abliterated need?
Q4_K_M is exactly 19,851,337,920 bytes (18.49 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Baichuan-M2-32B-abliterated's KV cache?
8.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 Baichuan-M2-32B-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.