eeve dpo v3 i1 needs about 8.6 GB of memory at Q4_K_M (a 6.5 GB file) with an 8K context window, so it fits on a 12 GB GPU. This repository has 24 quants, from 2.4 GB (IQ1_S) to 8.9 GB (Q6_K).
eeve dpo v3 i1 – a 10.8B llama model quantized for efficient inference
eeve dpo v3 i1 is a 10.8B parameter llama model fine‑tuned with DPO. It supports a 4096 token context window and is released under the apache-2.0 license. The model is available in multiple GGUF quantizations for different memory budgets.
Good at
- DPO fine‑tuning
- Large context handling
- Apache‑2.0 licensed
Limits
- No vision support
- Limited language coverage
- Requires 8k context for memory estimates
Best for
- Chatbots needing 8k context
- Research prototyping on limited GPU
- Educational demos
Who it’s for. Developers and researchers who need a llama model with DPO capabilities and a permissive license. The model is suitable for those who can run GGUF files on llama.cpp or similar runtimes.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ1_S | 2.4 GB | 3.7 GB | Fits | Get file → | |
| IQ1_M | 2.6 GB | 3.9 GB | Fits | Get file → | |
| IQ2_XXS | 3.0 GB | 4.3 GB | Fits | Get file → | |
| IQ2_XS | 3.3 GB | 4.6 GB | Fits | Get file → | |
| IQ2_S | 3.4 GB | 4.7 GB | Fits | Get file → | |
| IQ2_M | 3.7 GB | 5.0 GB | Fits | Get file → | |
| Q2_K_S | 3.8 GB | 5.1 GB | Fits | Get file → | |
| Q2_K | 4.0 GB | 5.4 GB | Fits | Get file → | |
| IQ3_XXS | 4.2 GB | 5.5 GB | Fits | Get file → | |
| IQ3_XS | 4.5 GB | 5.8 GB | Fits | Get file → | |
| Q3_K_S | 4.7 GB | 6.0 GB | Fits | Get file → | |
| IQ3_S | 4.7 GB | 6.0 GB | Fits | Get file → | |
| IQ3_M | 4.9 GB | 6.2 GB | Fits | Get file → | |
| Q3_K_M | 5.2 GB | 6.5 GB | Fits | Get file → | |
| Q3_K_L | 5.7 GB | 7.0 GB | Fits | Get file → | |
| IQ4_XS | 5.8 GB | 7.1 GB | Fits | Get file → | |
| Q4_0 | 6.1 GB | 7.5 GB | Tight | Get file → | |
| IQ4_NL | 6.1 GB | 7.5 GB | Tight | Get file → | |
| Q4_K_S | 6.2 GB | 7.5 GB | Tight | Get file → | |
| Q4_K_M | 6.5 GB | 7.8 GB | Tight | Get file → | |
| Q4_1 | 6.8 GB | 8.1 GB | Too big | Get file → | |
| Q5_K_S | 7.5 GB | 8.8 GB | Too big | Get file → | |
| Q5_K_M | 7.7 GB | 9.0 GB | Too big | Get file → | |
| Q6_K | 8.9 GB | 10.2 GB | Too big | Get file → |
For 8 GB VRAM, use IQ1_S (2.39 GB, 4.5 GB memory) or IQ1_M (2.6 GB, 4.7 GB memory). If 12 GB VRAM is available, Q4_K_M (6.51 GB, 8.6 GB memory) offers a good balance of size and performance. Higher‑quality quants like Q5_K_M or Q6_K require 9.8 GB or 11 GB memory respectively.
What GPU do you need for eeve dpo v3 i1?
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 Q2_K_S (3.8 GB file, about 5.9 GB in use).
- 8 GB VRAM: the best quant that fits is IQ4_XS (5.8 GB file, about 7.9 GB in use).
- 12 GB VRAM: the best quant that fits is Q6_K (8.9 GB file, about 11.0 GB in use).
Which eeve dpo v3 i1 quant should you choose?
Q4_K_M is the usual starting point for eeve dpo v3 i1: it balances file size and quality well. Here it is a 6.5 GB file.
If memory is tight, the smallest file is IQ1_S at 2.4 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
Source
Frequently asked questions about eeve dpo v3 i1
How much VRAM does eeve dpo v3 i1 need?
About 8.6 GB at Q4_K_M with an 8K context window. That is the 6.5 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 eeve dpo v3 i1 on an 8 GB GPU?
Yes, with IQ4_XS: the 5.8 GB file needs about 7.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of eeve dpo v3 i1 GGUF?
It depends on the quant: IQ1_S is 2.4 GB, IQ1_M is 2.6 GB, IQ2_XXS is 3.0 GB, IQ2_XS is 3.3 GB, IQ2_S is 3.4 GB, IQ2_M is 3.7 GB and 18 more.
What context length does eeve dpo v3 i1 support?
The GGUF header lists a trained context length of 4,096 tokens (4K). The KV cache grows with the context you use: about 1.6 GB at 8K and 0.8 GB at 4K.
Where can I download eeve dpo v3 i1 GGUF?
The files are on Hugging Face in the mradermacher/eeve_dpo-v3-i1-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 eeve dpo v3 i1 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.
Can I run eeve dpo v3 i1 on 8 GB VRAM?
Yes, the IQ1_S or IQ1_M quantizations fit within 8 GB VRAM, using approximately 4.5 GB or 4.7 GB memory at 8k context.
Does this model support vision tasks?
No, eeve dpo v3 i1 is a text‑only model with no vision capabilities.
What license applies to this model?
The model is released under the apache-2.0 license, allowing free use and modification.