Phi3 Text To Sql Merged needs about 6.1 GB of memory at Q4_K_M (a 2.4 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 2 quants, from 2.4 GB (Q4_K_M) to 2.8 GB (Q5_K_M).
Phi3 Text To Sql Merged is a 3.82B-parameter Phi model in GGUF format, quantized by Bhuvandesai. Its trained context length is 4K tokens. The repository has 2 quant files, from 2.4 GB (Q4_K_M) to 2.8 GB (Q5_K_M).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 2.4 GB | 4.5 GB | Fits | Get file → | |
| Q5_K_M | 2.8 GB | 4.9 GB | Fits | Get file → |
What GPU do you need for Phi3 Text To Sql 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: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: the best quant that fits is Q5_K_M (2.8 GB file, about 6.5 GB in use).
Which Phi3 Text To Sql Merged quant should you choose?
Q4_K_M is the usual starting point for Phi3 Text To Sql Merged: it balances file size and quality well. Here it is a 2.4 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Phi3 Text To Sql Merged
How much VRAM does Phi3 Text To Sql Merged need?
About 6.1 GB at Q4_K_M with an 8K context window. That is the 2.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 Phi3 Text To Sql Merged on an 8 GB GPU?
Yes, with Q5_K_M: the 2.8 GB file needs about 6.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Phi3 Text To Sql Merged GGUF?
It depends on the quant: Q4_K_M is 2.4 GB, Q5_K_M is 2.8 GB.
What context length does Phi3 Text To Sql Merged support?
The GGUF header lists a trained context length of 4,096 tokens (4K). The KV cache grows with the context you use: about 3.2 GB at 8K and 1.6 GB at 4K.
Where can I download Phi3 Text To Sql Merged GGUF?
The files are on Hugging Face in the Bhuvandesai/phi3-text-to-sql-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 Phi3 Text To Sql Merged use?
Hugging Face lists the license as mit. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.