Laguna-S-2.1
poolside/Laguna-S-2.1Laguna-S-2.1 at Q4_K_M is exactly 71,163,055,872 bytes (66.28 GiB / 71.16 GB) — an effective 4.843 bits per weight, not the nominal 4. Its KV cache at 32K is 1.64 GiB, not the 6.00 GiB a flat formula predicts.
Shipped quantizations
| Quant | Size● | Exact bytes● | Effective bpw● | Tensors● | Publisher |
|---|---|---|---|---|---|
| IQ1_S | 23.15 GiB | 24,856,209,600 | 1.691 | — | bartowski |
| IQ1_M | 25.75 GiB | 27,643,552,704 | 1.881 | — | bartowski |
| IQ2_XXS | 29.82 GiB | 32,016,494,784 | 2.179 | — | bartowski |
| UD-IQ1_S | 31.45 GiB | 33,766,781,984 | 2.298 | — | unsloth |
| IQ2_XS | 33.12 GiB | 35,565,180,096 | 2.420 | — | bartowski |
| UD-IQ1_M | 33.19 GiB | 35,641,635,872 | 2.425 | — | unsloth |
| IQ2_S | 33.77 GiB | 36,255,519,936 | 2.467 | — | bartowski |
| UD-IQ2_XXS | 34.64 GiB | 37,189,334,048 | 2.531 | — | unsloth |
| UD-IQ2_M | 34.71 GiB | 37,268,665,376 | 2.536 | — | unsloth |
| IQ2_M | 37.19 GiB | 39,930,034,368 | 2.717 | — | bartowski |
| Q2_K | 38.92 GiB | 41,785,156,032 | 2.843 | — | bartowski |
| Q2_K_L | 39.20 GiB | 42,086,212,032 | 2.864 | — | bartowski |
| UD-IQ3_XXS | 41.24 GiB | 44,282,842,016 | 3.013 | — | unsloth |
| UD-IQ3_S | 45.10 GiB | 48,428,911,520 | 3.296 | — | unsloth |
| IQ3_XXS | 46.07 GiB | 49,469,178,048 | 3.366 | — | bartowski |
| Q3_K_S | 48.03 GiB | 51,567,785,664 | 3.509 | — | bartowski |
| IQ3_XS2 shards | 50.29 GiB | 53,999,433,632 | 3.675 | — | bartowski |
| UD-Q3_K_M3 shards | 50.31 GiB | 54,019,158,688 | 3.676 | — | unsloth |
| Q3_K_M2 shards | 50.33 GiB | 54,037,477,280 | 3.677 | — | bartowski |
| Q3_K_L2 shards | 52.33 GiB | 56,187,287,456 | 3.824 | — | bartowski |
| IQ3_M2 shards | 52.60 GiB | 56,475,416,480 | 3.843 | — | bartowski |
| UD-IQ4_XS3 shards | 53.61 GiB | 57,566,704,320 | 3.917 | — | unsloth |
| UD-IQ4_NL3 shards | 54.71 GiB | 58,749,498,048 | 3.998 | — | unsloth |
| IQ4_XS2 shards | 58.98 GiB | 63,327,407,264 | 4.309 | — | bartowski |
| IQ4_NL2 shards | 62.32 GiB | 66,915,807,392 | 4.554 | — | bartowski |
| Q4_02 shards | 62.44 GiB | 67,042,422,944 | 4.562 | — | bartowski |
| UD-Q4_K_S3 shards | 63.88 GiB | 68,589,335,232 | 4.668 | — | unsloth |
| Q4_K_S2 shards | 64.36 GiB | 69,108,379,776 | 4.703 | — | bartowski |
| Q4_K_M2 shards | 66.28 GiB | 71,163,055,872 | 4.843 | — | lmstudio-community |
| Q4_K_M2 shards | 66.83 GiB | 71,759,147,168 | 4.883 | — | bartowski |
| UD-Q4_K_M3 shards | 68.10 GiB | 73,119,183,552 | 4.976 | — | unsloth |
| Q4_12 shards | 68.96 GiB | 74,043,062,432 | 5.039 | — | bartowski |
| Q5_K_S3 shards | 75.72 GiB | 81,299,489,056 | 5.532 | — | bartowski |
| UD-Q5_K_S3 shards | 76.98 GiB | 82,656,195,264 | 5.625 | — | unsloth |
| Q5_K_M3 shards | 78.22 GiB | 83,984,761,120 | 5.715 | — | bartowski |
| Q5_K_L3 shards | 78.39 GiB | 84,175,028,512 | 5.728 | — | bartowski |
| UD-Q5_K_M3 shards | 81.83 GiB | 87,859,229,344 | 5.979 | — | unsloth |
| Q4_K_M | 89.44 GiB | 96,031,829,760 | 6.535 | 814 | poolside |
| Q6_K3 shards | 89.93 GiB | 96,559,847,584 | 6.571 | — | lmstudio-community |
| UD-Q6_K3 shards | 91.19 GiB | 97,912,976,032 | 6.663 | — | unsloth |
KV cache by context
| Context | KV cache (f16)● | Flat formula | Overstated by | Full / windowed / recurrent |
|---|---|---|---|---|
| 4,096 | 0.33 GiB | 0.75 GiB | 2.29× | 12 / 36 / 0 |
| 8,192 | 0.52 GiB | 1.50 GiB | 2.91× | 12 / 36 / 0 |
| 16,384 | 0.89 GiB | 3.00 GiB | 3.37× | 12 / 36 / 0 |
| 32,768 | 1.64 GiB | 6.00 GiB | 3.66× | 12 / 36 / 0 |
| 65,536 | 3.14 GiB | 12.00 GiB | 3.82× | 12 / 36 / 0 |
| 131,072 | 6.14 GiB | 24.00 GiB | 3.91× | 12 / 36 / 0 |
36 of 48 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
Will it run on your card?
Why other calculators give a different number
A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 61.59 GiB. The real file is 66.28 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 6.00 GiB at 32K context where the real figure is 1.64 GiB, because most of this model's layers cache a fixed window rather than the whole context.
Architecture
Questions people ask
- How much VRAM does Laguna-S-2.1 need?
- Q4_K_M is exactly 71,163,055,872 bytes (66.28 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-S-2.1's KV cache?
- 1.64 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-S-2.1 a mixture-of-experts model?
- Yes — 256 experts, 10 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-S-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.