laya_multilingual_unsloth_dynamic needs about 1.1 GB of memory at Q4_K_M (a 0.5 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 3 quants, from 0.4 GB (Q8_0) to 0.7 GB (F16).
Multilingual decision model, 322M parameters, non‑autoregressive
laya_multilingual_unsloth_dynamic is a 322M‑parameter decision model compiled with ggmlc. It scores typed questions in a single forward pass and supports over 100 languages. The model is licensed under Apache‑2.0 and requires the ggmlc runtime, not llama.cpp.
Good at
- Fast multilingual decision making
- Non‑autoregressive inference
- Low memory footprint
Limits
- No text generation
- Limited to 1,024‑token context by default
- Requires ggmlc runtime
Best for
- Routing mixed‑language workloads
- Quick classification tasks
- Low‑latency inference on edge devices
Who it’s for. Developers building language‑aware routing systems or services that need fast, calibrated probabilities for non‑English text. The model is ideal for applications that require a single forward pass without token generation.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q8_0 | 0.4 GB | 0.9 GB | Fits | Get file → | |
| Q4_K_M | 0.5 GB | 1.1 GB | Fits | Get file → | |
| F16 | 0.7 GB | 1.2 GB | Fits | Get file → |
For 8 GB VRAM, the Q8_0 file (0.36 GB) uses about 0.9 GB memory at 8 k context. If more memory is available, Q4_K_M (0.52 GB) uses about 1.1 GB, and F16 (0.66 GB) uses about 1.2 GB. Choose the smallest quant that meets your memory budget.
What GPU do you need for laya_multilingual_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.7 GB file, about 1.2 GB in use).
Which laya_multilingual_unsloth_dynamic quant should you choose?
Q4_K_M is the usual starting point for laya_multilingual_unsloth_dynamic: it balances file size and quality well. Here it is a 0.5 GB file.
The Q8_0 file is 0.4 GB, about 0.7 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.
If memory is tight, the smallest file is Q8_0 at 0.4 GB, with the quality trade-offs that come with fewer bits. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about laya_multilingual_unsloth_dynamic
How much VRAM does laya_multilingual_unsloth_dynamic need?
About 1.1 GB at Q4_K_M with an 8K context window. That is the 0.5 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_multilingual_unsloth_dynamic on an 8 GB GPU?
Yes, with F16: the 0.7 GB file needs about 1.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of laya_multilingual_unsloth_dynamic GGUF?
It depends on the quant: Q8_0 is 0.4 GB, Q4_K_M is 0.5 GB, F16 is 0.7 GB.
Where can I download laya_multilingual_unsloth_dynamic GGUF?
The files are on Hugging Face in the ldov/laya-multilingual-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_multilingual_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 this model on 8 GB VRAM?
Yes, the Q8_0 quant uses about 0.9 GB memory at 8 k context, well within 8 GB VRAM.
Does this model generate text?
No, it is a decision model that returns probabilities for typed questions in a single forward pass.
What languages does it support?
It covers over 100 languages, designed for non‑English text.