DE

DeepSeek SQL Expert

DeepSeekGGUF by ukungUpdated 2024-05-20
Download on Hugging Face
Parameters1.35B
Context16K
Layers24
Architecturellama
Smallest quant0.6 GB
Quick answer

DeepSeek SQL Expert needs about 3.0 GB of memory at Q4_K_M (a 0.9 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 14 quants, from 0.6 GB (Q2_K) to 1.4 GB (Q8_0).

DeepSeek SQL Expert is a 1.35B-parameter DeepSeek model in GGUF format, quantized by ukung. Its trained context length is 16K tokens. The repository has 14 quant files, from 0.6 GB (Q2_K) to 1.4 GB (Q8_0).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K0.6 GB 2.7 GB
Fits Get file →
Q3_K_S0.6 GB 2.8 GB
Fits Get file →
Q3_K_M0.7 GB 2.8 GB
Fits Get file →
Q3_K_L0.7 GB 2.9 GB
Fits Get file →
Q4_00.8 GB 2.9 GB
Fits Get file →
Q4_K_S0.8 GB 2.9 GB
Fits Get file →
Q4_10.9 GB 3.0 GB
Fits Get file →
Q4_K_M0.9 GB 3.0 GB
Fits Get file →
Q5_00.9 GB 3.0 GB
Fits Get file →
Q5_K_S1.0 GB 3.1 GB
Fits Get file →
Q5_K_M1.0 GB 3.1 GB
Fits Get file →
Q5_11.0 GB 3.1 GB
Fits Get file →
Q6_K1.2 GB 3.3 GB
Fits Get file →
Q8_01.4 GB 3.5 GB
Fits Get file →

What GPU do you need for DeepSeek SQL Expert?

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 Q8_0 (1.4 GB file, about 3.5 GB in use).

Which DeepSeek SQL Expert quant should you choose?

Q4_K_M is the usual starting point for DeepSeek SQL Expert: it balances file size and quality well. Here it is a 0.9 GB file.

The Q8_0 file is 1.4 GB, about 1.6 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 Q2_K at 0.6 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturellama
Parameters1.35B
Layers24
Trained context16,384 tokens
KV cache (fp16)192 KB per token

Source

Quantized byukung
FamilyDeepSeek
Licenseapache-2.0
Downloads (HF)158
Last updated2024-05-20

Frequently asked questions about DeepSeek SQL Expert

How much VRAM does DeepSeek SQL Expert need?

About 3.0 GB at Q4_K_M with an 8K context window. That is the 0.9 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 DeepSeek SQL Expert on an 8 GB GPU?

Yes, with Q8_0: the 1.4 GB file needs about 3.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of DeepSeek SQL Expert GGUF?

It depends on the quant: Q2_K is 0.6 GB, Q3_K_S is 0.6 GB, Q3_K_M is 0.7 GB, Q3_K_L is 0.7 GB, Q4_0 is 0.8 GB, Q4_K_S is 0.8 GB and 8 more.

What context length does DeepSeek SQL Expert support?

The GGUF header lists a trained context length of 16,384 tokens (16K). The KV cache grows with the context you use: about 1.6 GB at 8K and 3.2 GB at 16K.

Where can I download DeepSeek SQL Expert GGUF?

The files are on Hugging Face in the ukung/DeepSeek-SQL-Expert-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 DeepSeek SQL Expert 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 ukung

All by ukung →

More DeepSeek models

All DeepSeek →

Other tiny models

All tiny models →