deepseek-ai · text

deepseek-coder-5.7bmqa-base

deepseek-ai/deepseek-coder-5.7bmqa-base

deepseek-coder-5.7bmqa-base at Q4_K_M is exactly 3,430,867,168 bytes (3.20 GiB / 3.43 GB) — an effective 4.815 bits per weight, not the nominal 4. Its KV cache at 32K is 0.50 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
5.7B
Architecture
llama
32 layers
Context
16,384
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K2.00 GiB2,142,595,3283.007tensorblock
Q2_K2.27 GiB2,433,573,0883.415TheBloke
Q3_K_S2.33 GiB2,503,221,4723.513TheBloke
Q3_K_M2.59 GiB2,779,654,4003.901tensorblock
Q3_K_M2.59 GiB2,779,783,3923.901TheBloke
Q3_K_L2.81 GiB3,017,941,2164.236TheBloke
Q4_03.02 GiB3,242,713,3124.551TheBloke
Q4_K_S3.04 GiB3,265,519,8404.583TheBloke
Q4_K_M3.20 GiB3,430,867,1684.815TheBloke
Q5_K_S3.67 GiB3,938,705,6325.528TheBloke
Q5_03.67 GiB3,938,705,6325.528TheBloke
Q5_K_M3.76 GiB4,035,633,3765.664TheBloke
Q6_K4.36 GiB4,678,197,4726.566TheBloke
Q8_05.64 GiB6,058,680,5448.503TheBloke

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.06 GiB0.06 GiB32 / 0 / 0
8,1920.13 GiB0.13 GiB32 / 0 / 0
16,3840.25 GiB0.25 GiB32 / 0 / 0
32,7680.50 GiB0.50 GiB32 / 0 / 0
65,5361.00 GiB1.00 GiB32 / 0 / 0
131,0722.00 GiB2.00 GiB32 / 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 2.99 GiB. The real file is 3.20 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

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

Questions people ask

How much VRAM does deepseek-coder-5.7bmqa-base need?
Q4_K_M is exactly 3,430,867,168 bytes (3.20 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is deepseek-coder-5.7bmqa-base's KV cache?
0.50 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 deepseek-coder-5.7bmqa-base 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.