duckdb nsql needs about 8.6 GB of memory at its main file (a 3.8 GB file) with an 8K context window, so it fits on a 12 GB GPU.
duckdb nsql is a 6.74B-parameter Duckdb model in GGUF format, quantized by apurv0405. Its trained context length is 16K tokens. The repository has 1 quant file, from 3.8 GB to 3.8 GB.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 3.8 GB | 8.6 GB | Too big | Get file → |
What GPU do you need for duckdb nsql?
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: the best quant that fits is the main file (3.8 GB file, about 8.6 GB in use).
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about duckdb nsql
How much VRAM does duckdb nsql need?
About 8.6 GB at its main file with an 8K context window. That is the 3.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 duckdb nsql on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 8.6 GB, so you would need a larger GPU or CPU offloading.
What is the file size of duckdb nsql GGUF?
It depends on the quant: file is 3.8 GB.
What context length does duckdb nsql support?
The GGUF header lists a trained context length of 16,384 tokens (16K). The KV cache grows with the context you use: about 4.3 GB at 8K and 8.6 GB at 16K.
Where can I download duckdb nsql GGUF?
The files are on Hugging Face in the apurv0405/duckdb-nsql-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.