poolside · text · mixture of experts

Laguna-XS-2.1

poolside/Laguna-XS-2.1

Laguna-XS-2.1 at Q4_K_M is exactly 20,274,299,936 bytes (18.88 GiB / 20.27 GB) — an effective 4.850 bits per weight, not the nominal 4. Its KV cache at 32K is 1.37 GiB, not the 5.00 GiB a flat formula predicts.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
33.4B
total, not active
Architecture
laguna
40 layers
Context
262,144
native (config.json)
License
openmdw-1.1

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
IQ2_XXS8.76 GiB9,404,976,0002.250bartowski
IQ2_XS9.67 GiB10,386,596,7362.485bartowski
IQ2_S9.89 GiB10,620,330,8802.541bartowski
IQ2_M10.84 GiB11,635,506,0482.783bartowski
Q2_K11.32 GiB12,157,833,6002.908bartowski
Q2_K_L11.51 GiB12,358,537,6002.956bartowski
IQ3_XXS13.30 GiB14,285,958,0163.417bartowski
Q3_K_S13.87 GiB14,894,198,6563.563bartowski
IQ3_XS14.49 GiB15,563,714,4323.723bartowski
Q3_K_M14.51 GiB15,575,904,1283.726678bartowski
Q3_K_L15.02 GiB16,129,879,9363.858bartowski
IQ3_M15.16 GiB16,282,120,0643.895bartowski
IQ4_XS16.96 GiB18,211,212,6724.356678bartowski
Q4_017.89 GiB19,210,003,8404.595678bartowski
IQ4_NL17.89 GiB19,212,625,2804.596bartowski
Q4_K_S18.42 GiB19,781,477,7604.732bartowski
Q4_K_M18.88 GiB20,274,299,9364.850lmstudio-community
Q4_K_M18.88 GiB20,274,300,0324.850678poolside
Q4_K_M19.14 GiB20,548,085,1204.915678bartowski
Q4_K_L19.28 GiB20,700,620,1604.952bartowski
Q4_119.73 GiB21,183,993,2165.067bartowski
Q5_K_S21.63 GiB23,226,631,5525.556bartowski
Q5_K_M22.36 GiB24,005,035,3925.742678bartowski
Q5_K_L22.47 GiB24,131,880,3205.773bartowski
Q6_K25.61 GiB27,502,729,7606.579678lmstudio-community
Q6_K27.04 GiB29,036,854,1446.946678bartowski
Q6_K_L27.14 GiB29,136,403,3286.970bartowski
Q8_033.15 GiB35,597,116,4488.515678lmstudio-community
Q8_033.15 GiB35,597,116,8008.515678bartowski
BF1662.33 GiB66,930,226,30416.011poolside
BF162 shards62.33 GiB66,930,226,49616.011bartowski

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.27 GiB0.63 GiB2.29×10 / 30 / 0
8,1920.43 GiB1.25 GiB2.91×10 / 30 / 0
16,3840.74 GiB2.50 GiB3.37×10 / 30 / 0
32,7681.37 GiB5.00 GiB3.66×10 / 30 / 0
65,5362.62 GiB10.00 GiB3.82×10 / 30 / 0
131,0725.12 GiB20.00 GiB3.91×10 / 30 / 0

30 of 40 layers cache only a 512-token window rather than the full context, on a period of 4. Figures assume the default configuration; --swa-full disables the saving entirely.

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.52 GiB. The real file is 18.88 GiB, because a quantization is a mixture and some tensors are always kept at higher precision. The larger discrepancy is the cache: a flat formula gives 5.00 GiB at 32K context where the real figure is 1.37 GiB, because most of this model's layers cache a fixed window rather than the whole context.

Architecture

from config.json
Layers
40
Attention heads
48
KV heads
8
Head dim
128
Hidden size
2048
Vocab
100,352
Sliding window
512
SWA period
4
MLA
no
Experts
256
Experts per token
8
use_sliding_window

Questions people ask

How much VRAM does Laguna-XS-2.1 need?
Q4_K_M is exactly 20,274,299,936 bytes (18.88 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Laguna-XS-2.1's KV cache?
1.37 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.
Is Laguna-XS-2.1 a mixture-of-experts model?
Yes — 256 experts, 8 routed per token. Every expert must be resident, but only the routed ones are read per token, which is why its memory requirement and its speed behave very differently.
Which quantization of Laguna-XS-2.1 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.