Llamacpp imatrix Quantizations of MadWizard-SFT-v2-Mistral-7b-v0.3

Using llama.cpp release b3152 for quantization.

Original model: https://huggingface.co/Lumpen1/MadWizard-SFT-v2-Mistral-7b-v0.3

All quants made using imatrix option with dataset from here

Prompt format

<|im_start|> system
{system_prompt}<|im_end|> 
<|im_start|> user
{prompt}<|im_end|> 
<|im_start|> assistant

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

Filename Quant type File Size Description
MadWizard-SFT-v2-Mistral-7b-v0.3-Q8_0_L.gguf Q8_0_L 7.95GB Experimental, uses f16 for embed and output weights. Please provide any feedback of differences. Extremely high quality, generally unneeded but max available quant.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q8_0.gguf Q8_0 7.70GB Extremely high quality, generally unneeded but max available quant.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q6_K_L.gguf Q6_K_L 6.26GB Experimental, uses f16 for embed and output weights. Please provide any feedback of differences. Very high quality, near perfect, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q6_K.gguf Q6_K 5.94GB Very high quality, near perfect, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q5_K_L.gguf Q5_K_L 5.47GB Experimental, uses f16 for embed and output weights. Please provide any feedback of differences. High quality, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q5_K_M.gguf Q5_K_M 5.13GB High quality, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q5_K_S.gguf Q5_K_S 5.00GB High quality, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q4_K_L.gguf Q4_K_L 4.72GB Experimental, uses f16 for embed and output weights. Please provide any feedback of differences. Good quality, uses about 4.83 bits per weight, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q4_K_M.gguf Q4_K_M 4.37GB Good quality, uses about 4.83 bits per weight, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q4_K_S.gguf Q4_K_S 4.14GB Slightly lower quality with more space savings, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-IQ4_XS.gguf IQ4_XS 3.91GB Decent quality, smaller than Q4_K_S with similar performance, recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q3_K_L.gguf Q3_K_L 3.82GB Lower quality but usable, good for low RAM availability.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q3_K_M.gguf Q3_K_M 3.52GB Even lower quality.
MadWizard-SFT-v2-Mistral-7b-v0.3-IQ3_M.gguf IQ3_M 3.28GB Medium-low quality, new method with decent performance comparable to Q3_K_M.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q3_K_S.gguf Q3_K_S 3.16GB Low quality, not recommended.
MadWizard-SFT-v2-Mistral-7b-v0.3-IQ3_XS.gguf IQ3_XS 3.02GB Lower quality, new method with decent performance, slightly better than Q3_K_S.
MadWizard-SFT-v2-Mistral-7b-v0.3-IQ3_XXS.gguf IQ3_XXS 2.83GB Lower quality, new method with decent performance, comparable to Q3 quants.
MadWizard-SFT-v2-Mistral-7b-v0.3-Q2_K.gguf Q2_K 2.72GB Very low quality but surprisingly usable.
MadWizard-SFT-v2-Mistral-7b-v0.3-IQ2_M.gguf IQ2_M 2.50GB Very low quality, uses SOTA techniques to also be surprisingly usable.
MadWizard-SFT-v2-Mistral-7b-v0.3-IQ2_S.gguf IQ2_S 2.31GB Very low quality, uses SOTA techniques to be usable.
MadWizard-SFT-v2-Mistral-7b-v0.3-IQ2_XS.gguf IQ2_XS 2.20GB Very low quality, uses SOTA techniques to be usable.

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/MadWizard-SFT-v2-Mistral-7b-v0.3-GGUF --include "MadWizard-SFT-v2-Mistral-7b-v0.3-Q4_K_M.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/MadWizard-SFT-v2-Mistral-7b-v0.3-GGUF --include "MadWizard-SFT-v2-Mistral-7b-v0.3-Q8_0.gguf/*" --local-dir MadWizard-SFT-v2-Mistral-7b-v0.3-Q8_0

You can either specify a new local-dir (MadWizard-SFT-v2-Mistral-7b-v0.3-Q8_0) 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 'QX_K_X', like Q5_K_M.

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 IQX_X, like IQ3_M. 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

Downloads last month
179
GGUF
Model size
7.25B params
Architecture
llama

2-bit

3-bit

4-bit

5-bit

6-bit

8-bit

32-bit

Inference Examples
This model does not have enough activity to be deployed to Inference API (serverless) yet. Increase its social visibility and check back later, or deploy to Inference Endpoints (dedicated) instead.