laya_english_unsloth_dynamic needs about 1.0 GB of memory at Q4_K_M (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 3 quants, from 0.4 GB (Q4_K_M) to 0.8 GB (F16).
Laya English GGUF – a non‑autoregressive decision model
Laya English GGUF is a 0.422 B parameter model compiled with ggmlc. It scores typed questions in a single forward pass and returns calibrated probabilities. The model is licensed under Apache‑2.0 and is not compatible with llama.cpp.
Good at
- Fast single‑pass decision scoring
- Calibrated probability outputs
- No text generation
Limits
- No vision support
- Limited to English only
- Requires ggmlc runtime
Best for
- Email routing decisions
- Jailbreak/injection guard checks
- Expense and invoice gatekeeping
Who it’s for. Developers building decision‑making services that need quick, reliable probability estimates without text generation. Suitable for backend pipelines and agent harnesses where calibrated scores are required.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.4 GB | 1.0 GB | Fits | Get file → | |
| Q8_0 | 0.5 GB | 1.0 GB | Fits | Get file → | |
| F16 | 0.8 GB | 1.4 GB | Fits | Get file → |
For 8 GB VRAM, use Q4_K_M (0.42 GB file, ~1 GB RAM). Q8_0 (0.45 GB) offers higher precision with similar memory. F16 (0.85 GB) needs more memory but provides full‑precision scores. Estimates are approximate.
What GPU do you need for laya_english_unsloth_dynamic?
These figures add the file size, an fp16 KV cache at an 8K context window 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: the best quant that fits is F16 (0.8 GB file, about 1.4 GB in use).
Which laya_english_unsloth_dynamic quant should you choose?
Q4_K_M is the usual starting point for laya_english_unsloth_dynamic: it balances file size and quality well. Here it is a 0.4 GB file.
The Q8_0 file is 0.5 GB, about 1.1 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
Source
Frequently asked questions about laya_english_unsloth_dynamic
How much VRAM does laya_english_unsloth_dynamic need?
About 1.0 GB at Q4_K_M with an 8K context window. That is the 0.4 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 laya_english_unsloth_dynamic on an 8 GB GPU?
Yes, with F16: the 0.8 GB file needs about 1.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of laya_english_unsloth_dynamic GGUF?
It depends on the quant: Q4_K_M is 0.4 GB, Q8_0 is 0.5 GB, F16 is 0.8 GB.
Where can I download laya_english_unsloth_dynamic GGUF?
The files are on Hugging Face in the mys/laya-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 laya_english_unsloth_dynamic 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.
Can I run Laya English GGUF on 8 GB VRAM?
Yes. The Q4_K_M quant uses about 1 GB of VRAM, fitting comfortably on 8 GB.
Does this model support other languages?
No. The English checkpoint is limited to English; use laya‑multilingual‑GGUF for other languages.
Is it compatible with llama.cpp?
No. The GGUF files are produced by ggmlc and cannot be loaded in llama.cpp.