Datalevin Nlq Merged needs about 1.2 GB of memory at its main file (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU.
Datalevin Nlq Merged is a 362M-parameter Datalevin model in GGUF format, quantized by kbosompem. Its trained context length is 8K tokens. The repository has 1 quant file, from 0.4 GB to 0.4 GB.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.4 GB | 1.2 GB | Fits | Get file → |
What GPU do you need for Datalevin Nlq 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: the best quant that fits is the main file (0.4 GB file, about 1.2 GB in use).
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Datalevin Nlq Merged
How much VRAM does Datalevin Nlq Merged need?
About 1.2 GB at its main file 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 Datalevin Nlq Merged on an 8 GB GPU?
Yes, with the smaller files: the 0.4 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 Datalevin Nlq Merged GGUF?
It depends on the quant: file is 0.4 GB.
What context length does Datalevin Nlq Merged support?
The GGUF header lists a trained context length of 8,192 tokens (8K). The KV cache grows with the context you use: about 0.3 GB at 8K and 0.3 GB at 8K.
Where can I download Datalevin Nlq Merged GGUF?
The files are on Hugging Face in the kbosompem/datalevin-nlq-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.