XiaomiMiMo.MiMo V2.5 Pro needs about 668.6 GB of memory at Q4_K_M (a 619.2 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 5 quants, from 374.3 GB (Q2_K) to 839.9 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 196.0 GB.
XiaomiMiMo.MiMo V2.5 Pro is a 1020B-parameter Mimo model in GGUF format, quantized by DevQuasar. Its trained context length is 1024K tokens. The repository has 5 quant files, from 374.3 GB (Q2_K) to 839.9 GB (Q6_K).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 374.3 GB (26 parts) | 423.8 GB | Too big | Get file → | |
| Q3_K_M | 489.4 GB (35 parts) | 538.9 GB | Too big | Get file → | |
| Q4_K_M | 619.2 GB (43 parts) | 668.6 GB | Too big | Get file → | |
| Q5_K_M | 726.2 GB (52 parts) | 775.7 GB | Too big | Get file → | |
| Q6_K | 839.9 GB (69 parts) | 889.3 GB | Too big | Get file → |
What GPU do you need for XiaomiMiMo.MiMo V2.5 Pro?
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: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: no quant fits at an 8K context.
- 32 GB VRAM: no quant fits at an 8K context.
- 48 GB VRAM: no quant fits at an 8K context.
Which XiaomiMiMo.MiMo V2.5 Pro quant should you choose?
Q4_K_M is the usual starting point for XiaomiMiMo.MiMo V2.5 Pro: it balances file size and quality well. Here it is a 619.2 GB file.
If memory is tight, the smallest file is Q2_K at 374.3 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 XiaomiMiMo.MiMo V2.5 Pro
How much VRAM does XiaomiMiMo.MiMo V2.5 Pro need?
About 668.6 GB at Q4_K_M with an 8K context window. That is the 619.2 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 XiaomiMiMo.MiMo V2.5 Pro on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 423.8 GB, so you would need a larger GPU or CPU offloading.
What is the file size of XiaomiMiMo.MiMo V2.5 Pro GGUF?
It depends on the quant: Q2_K is 374.3 GB, Q3_K_M is 489.4 GB, Q4_K_M is 619.2 GB, Q5_K_M is 726.2 GB, Q6_K is 839.9 GB.
What context length does XiaomiMiMo.MiMo V2.5 Pro support?
The GGUF header lists a trained context length of 1,048,576 tokens (1024K). The KV cache grows with the context you use: about 49.0 GB at 8K and 196.0 GB at 32K.
Where can I download XiaomiMiMo.MiMo V2.5 Pro GGUF?
The files are on Hugging Face in the DevQuasar/XiaomiMiMo.MiMo-V2.5-Pro-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 XiaomiMiMo.MiMo V2.5 Pro 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.