ReadyArt · text

Melody1437-27B

ReadyArt/Melody1437-27B

Melody1437-27B at Q4_K_M is exactly 36,948,915,200 bytes (34.41 GiB / 36.95 GB) — an effective 10.640 bits per weight, not the nominal 4. Its KV cache at 32K is 2.00 GiB.

From the file· summed from 2 file(s)From the file· KV per layer
Parameters
27.8B
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
Q6_K23.68 GiB25,430,704,6407.323ReadyArt
Q3_K_M2 shards28.40 GiB30,497,817,6008.782ReadyArt
Q4_K_M2 shards34.41 GiB36,948,915,20010.640ReadyArt
Q5_K_M2 shards39.34 GiB42,239,964,16012.164ReadyArt
Q8_03 shards59.27 GiB63,642,044,96018.326ReadyArt

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.55 GiB. The real file is 34.41 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 Melody1437-27B need?
Q4_K_M is exactly 36,948,915,200 bytes (34.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 Melody1437-27B'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 Melody1437-27B 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.