SI

Silo Moe Merged

SiloGGUF by ksjpswaroopUpdated 2025-10-27
Download on Hugging Face
Parameters20.9B
Context128K
Layers24
Architecturegpt-oss
Smallest quant15.8 GB
Quick answer

Silo Moe Merged needs about 16.7 GB of memory at Q4_K_M (a 15.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 5 quants, from 15.8 GB (Q4_K_M) to 41.9 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.6 GB.

Silo Moe Merged is a 20.9B-parameter Silo model in GGUF format, quantized by ksjpswaroop. Its trained context length is 128K tokens. The repository has 5 quant files, from 15.8 GB (Q4_K_M) to 41.9 GB (F16).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q4_K_M15.8 GB 16.7 GB
Too big Get file →
Q5_K_M16.9 GB 17.8 GB
Too big Get file →
Q6_K22.2 GB 23.1 GB
Too big Get file →
Q8_022.3 GB 23.2 GB
Too big Get file →
F1641.9 GB 42.8 GB
Too big Get file →

What GPU do you need for Silo Moe Merged?

These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.

  • 4 GB VRAM: no quant fits at an 8K context.
  • 6 GB VRAM: no quant fits at an 8K context.
  • 8 GB VRAM: no quant fits at an 8K context.
  • 12 GB VRAM: no quant fits at an 8K context.
  • 16 GB VRAM: no quant fits at an 8K context.
  • 24 GB VRAM: the best quant that fits is Q8_0 (22.3 GB file, about 23.2 GB in use).
  • 32 GB VRAM: the best quant that fits is Q8_0 (22.3 GB file, about 23.2 GB in use).
  • 48 GB VRAM: the best quant that fits is F16 (41.9 GB file, about 42.8 GB in use).

Which Silo Moe Merged quant should you choose?

Q4_K_M is the usual starting point for Silo Moe Merged: it balances file size and quality well. Here it is a 15.8 GB file.

The Q8_0 file is 22.3 GB, about 1.4 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturegpt-oss
Parameters20.9B (approximate, mixture of experts)
Layers24
Trained context131,072 tokens
KV cache (fp16)48 KB per token

Source

Quantized byksjpswaroop
FamilySilo
Licenseapache-2.0
Downloads (HF)71
Last updated2025-10-27

Frequently asked questions about Silo Moe Merged

How much VRAM does Silo Moe Merged need?

About 16.7 GB at Q4_K_M with an 8K context window. That is the 15.8 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.

Can I run Silo Moe Merged on an 8 GB GPU?

Not at an 8K context. The smallest file needs about 16.7 GB, so you would need a larger GPU or CPU offloading.

What is the file size of Silo Moe Merged GGUF?

It depends on the quant: Q4_K_M is 15.8 GB, Q5_K_M is 16.9 GB, Q6_K is 22.2 GB, Q8_0 is 22.3 GB, F16 is 41.9 GB.

What context length does Silo Moe Merged support?

The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.6 GB at 32K.

Where can I download Silo Moe Merged GGUF?

The files are on Hugging Face in the ksjpswaroop/silo-moe-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does Silo Moe Merged use?

Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.

Similar models

Browse all →

More from ksjpswaroop

All by ksjpswaroop →

Other medium models

All medium models →