bartowski/MiniCPM-V-2_6-GGUF

---

basemodel: openbmb/MiniCPM-V-26 datasets:

• openbmb/RLAIF-V-Dataset

language:

• multilingual

library_name: transformers pipeline_tag: image-text-to-text tags:

• minicpm-v
• vision
• ocr
• multi-image
• video
• custom_code

quantized_by: bartowski

---

Llamacpp imatrix Quantizations of MiniCPM-V-2_6

Using llama.cpp release b3615 for quantization.

Original model: https://huggingface.co/openbmb/MiniCPM-V-2_6

All quants made using imatrix option with dataset from here

Run them in LM Studio

Prompt format

<|im_start|>system
{systemprompt}<|imend|>
<|im_start|>user
{prompt}<|im_end|>
<|im_start|>assistant

What's new:

Applying imatrix, should improve the text portion of the model

Download a file (not the whole branch) from below:

Filename	Quant type	File Size	Split	Description
MiniCPM-V-26-f16.gguf	f16	15.23GB	false	Full F16 weights.
MiniCPM-V-26-Q80.gguf	Q8_0	8.10GB	false	Extremely high quality, generally unneeded but max available quant.
MiniCPM-V-26-Q6KL.gguf	Q6KL	6.52GB	false	Uses Q8_0 for embed and output weights. Very high quality, near perfect, recommended.
MiniCPM-V-26-Q6K.gguf	Q6_K	6.25GB	false	Very high quality, near perfect, recommended.
MiniCPM-V-26-Q5KL.gguf	Q5KL	5.78GB	false	Uses Q8_0 for embed and output weights. High quality, recommended.
MiniCPM-V-26-Q5KM.gguf	Q5KM	5.44GB	false	High quality, recommended.
MiniCPM-V-26-Q5KS.gguf	Q5KS	5.31GB	false	High quality, recommended.
MiniCPM-V-26-Q4KL.gguf	Q4KL	5.08GB	false	Uses Q8_0 for embed and output weights. Good quality, recommended.
MiniCPM-V-26-Q4KM.gguf	Q4KM	4.68GB	false	Good quality, default size for must use cases, recommended.
MiniCPM-V-26-Q3KXL.gguf	Q3KXL	4.56GB	false	Uses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability.
MiniCPM-V-26-Q4KS.gguf	Q4KS	4.46GB	false	Slightly lower quality with more space savings, recommended.
MiniCPM-V-26-IQ4XS.gguf	IQ4XS	4.22GB	false	Decent quality, smaller than Q4K_S with similar performance, recommended.
MiniCPM-V-26-Q3KL.gguf	Q3KL	4.09GB	false	Lower quality but usable, good for low RAM availability.
MiniCPM-V-26-Q3KM.gguf	Q3KM	3.81GB	false	Low quality.
MiniCPM-V-26-IQ3M.gguf	IQ3M	3.57GB	false	Medium-low quality, new method with decent performance comparable to Q3K_M.
MiniCPM-V-26-Q2KL.gguf	Q2KL	3.55GB	false	Uses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
MiniCPM-V-26-Q3KS.gguf	Q3KS	3.49GB	false	Low quality, not recommended.
MiniCPM-V-26-IQ3XS.gguf	IQ3XS	3.34GB	false	Lower quality, new method with decent performance, slightly better than Q3K_S.
MiniCPM-V-26-Q2K.gguf	Q2_K	3.01GB	false	Very low quality but surprisingly usable.
MiniCPM-V-26-IQ2M.gguf	IQ2_M	2.78GB	false	Relatively low quality, uses SOTA techniques to be surprisingly usable.

Embed/output weights

Some of these quants (Q3KXL, Q4KL etc) are the standard quantization method with the embeddings and output weights quantized to Q8_0 instead of what they would normally default to.

Some say that this improves the quality, others don't notice any difference. If you use these models PLEASE COMMENT with your findings. I would like feedback that these are actually used and useful so I don't keep uploading quants no one is using.

Thanks!

Credits

Thank you kalomaze and Dampf for assistance in creating the imatrix calibration dataset

Thank you ZeroWw for the inspiration to experiment with embed/output

Downloading using huggingface-cli

First, make sure you have hugginface-cli installed:

pip install -U "huggingface_hub[cli]"

Then, you can target the specific file you want:

huggingface-cli download bartowski/MiniCPM-V-26-GGUF --include "MiniCPM-V-26-Q4KM.gguf" --local-dir ./

If the model is bigger than 50GB, it will have been split into multiple files. In order to download them all to a local folder, run:

huggingface-cli download bartowski/MiniCPM-V-26-GGUF --include "MiniCPM-V-26-Q8_0/*" --local-dir ./

You can either specify a new local-dir (MiniCPM-V-26-Q80) or download them all in place (./)

Which file should I choose?

A great write up with charts showing various performances is provided by Artefact2 here

The first thing to figure out is how big a model you can run. To do this, you'll need to figure out how much RAM and/or VRAM you have.

If you want your model running as FAST as possible, you'll want to fit the whole thing on your GPU's VRAM. Aim for a quant with a file size 1-2GB smaller than your GPU's total VRAM.

If you want the absolute maximum quality, add both your system RAM and your GPU's VRAM together, then similarly grab a quant with a file size 1-2GB Smaller than that total.

Next, you'll need to decide if you want to use an 'I-quant' or a 'K-quant'.

If you don't want to think too much, grab one of the K-quants. These are in format 'QXKX', like Q5KM.

If you want to get more into the weeds, you can check out this extremely useful feature chart:

llama.cpp feature matrix

But basically, if you're aiming for below Q4, and you're running cuBLAS (Nvidia) or rocBLAS (AMD), you should look towards the I-quants. These are in format IQXX, like IQ3M. These are newer and offer better performance for their size.

These I-quants can also be used on CPU and Apple Metal, but will be slower than their K-quant equivalent, so speed vs performance is a tradeoff you'll have to decide.

The I-quants are not compatible with Vulcan, which is also AMD, so if you have an AMD card double check if you're using the rocBLAS build or the Vulcan build. At the time of writing this, LM Studio has a preview with ROCm support, and other inference engines have specific builds for ROCm.

Want to support my work? Visit my ko-fi page here: https://ko-fi.com/bartowski