Phi35_Medqa_Dpo_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 4 quants, from 2.2 GB (Q4_0) to 7.6 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 12.9 GB.
Phi35_Medqa_Dpo_Merged is a 3.82B-parameter Phi model in GGUF format, quantized by olusegunola. Its trained context length is 128K tokens. The repository has 4 quant files, from 2.2 GB (Q4_0) to 7.6 GB (F16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_0 | 2.2 GB | 5.9 GB | Fits | Get file → | |
| Q4_K_M | 2.4 GB | 6.1 GB | Fits | Get file → | |
| Q8_0 | 4.1 GB | 7.8 GB | Tight | Get file → | |
| F16 | 7.6 GB | 11.4 GB | Too big | Get file → |
What GPU do you need for Phi35_Medqa_Dpo_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: the best quant that fits is Q4_0 (2.2 GB file, about 5.9 GB in use).
- 8 GB VRAM: the best quant that fits is Q8_0 (4.1 GB file, about 7.8 GB in use).
- 12 GB VRAM: the best quant that fits is F16 (7.6 GB file, about 11.4 GB in use).
Which Phi35_Medqa_Dpo_Merged quant should you choose?
Q4_K_M is the usual starting point for Phi35_Medqa_Dpo_Merged: it balances file size and quality well. Here it is a 2.4 GB file.
The Q8_0 file is 4.1 GB, about 1.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 Q4_0 at 2.2 GB, with the quality trade-offs that come with fewer bits. The usual sweet spot between file size and quality, and the quant most people start with.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Phi35_Medqa_Dpo_Merged
How much VRAM does Phi35_Medqa_Dpo_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 Phi35_Medqa_Dpo_Merged on an 8 GB GPU?
Yes, with Q8_0: the 4.1 GB file needs about 7.8 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Phi35_Medqa_Dpo_Merged GGUF?
It depends on the quant: Q4_0 is 2.2 GB, Q4_K_M is 2.4 GB, Q8_0 is 4.1 GB, F16 is 7.6 GB.
What context length does Phi35_Medqa_Dpo_Merged support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 3.2 GB at 8K and 12.9 GB at 32K.
Where can I download Phi35_Medqa_Dpo_Merged GGUF?
The files are on Hugging Face in the olusegunola/phi35-medqa-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.