CoolFace
Modelpublic

bartowski/Q2.5-MS-Mistoria-72b-v2-GGUF

sourceHugging Faceupdated 2y agoView on Hugging Face
2likes1.4kdownloads
Model Card

Llamacpp imatrix Quantizations of Q2.5-MS-Mistoria-72b-v2

Using <a href="https://github.com/ggerganov/llama.cpp/">llama.cpp</a> release <a href="https://github.com/ggerganov/llama.cpp/releases/tag/b4132">b4132</a> for quantization.

Original model: https://huggingface.co/Steelskull/Q2.5-MS-Mistoria-72b-v2

All quants made using imatrix option with dataset from here

Run them in LM Studio

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:

FilenameQuant typeFile SizeSplitDescription
Q2.5-MS-Mistoria-72b-v2-Q8_0.ggufQ8_077.26GBtrueExtremely high quality, generally unneeded but max available quant.
Q2.5-MS-Mistoria-72b-v2-Q6_K.ggufQ6_K64.35GBtrueVery high quality, near perfect, recommended.
Q2.5-MS-Mistoria-72b-v2-Q5_K_M.ggufQ5KM54.45GBtrueHigh quality, recommended.
Q2.5-MS-Mistoria-72b-v2-Q5_K_S.ggufQ5KS51.38GBtrueHigh quality, recommended.
Q2.5-MS-Mistoria-72b-v2-Q4_K_M.ggufQ4KM47.42GBfalseGood quality, default size for most use cases, recommended.
Q2.5-MS-Mistoria-72b-v2-Q4_K_S.ggufQ4KS43.89GBfalseSlightly lower quality with more space savings, recommended.
Q2.5-MS-Mistoria-72b-v2-Q4_0.ggufQ4_041.38GBfalseLegacy format, generally not worth using over similarly sized formats
Q2.5-MS-Mistoria-72b-v2-Q4_0_8_8.ggufQ408_841.23GBfalseOptimized for ARM and AVX inference. Requires 'sve' support for ARM (see details below). Don't use on Mac.
Q2.5-MS-Mistoria-72b-v2-Q3_K_XL.ggufQ3KXL40.60GBfalseUses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability.
Q2.5-MS-Mistoria-72b-v2-IQ4_XS.ggufIQ4_XS39.71GBfalseDecent quality, smaller than Q4KS with similar performance, recommended.
Q2.5-MS-Mistoria-72b-v2-Q3_K_L.ggufQ3KL39.51GBfalseLower quality but usable, good for low RAM availability.
Q2.5-MS-Mistoria-72b-v2-Q3_K_M.ggufQ3KM37.70GBfalseLow quality.
Q2.5-MS-Mistoria-72b-v2-IQ3_M.ggufIQ3_M35.50GBfalseMedium-low quality, new method with decent performance comparable to Q3KM.
Q2.5-MS-Mistoria-72b-v2-Q3_K_S.ggufQ3KS34.49GBfalseLow quality, not recommended.
Q2.5-MS-Mistoria-72b-v2-IQ3_XXS.ggufIQ3_XXS31.85GBfalseLower quality, new method with decent performance, comparable to Q3 quants.
Q2.5-MS-Mistoria-72b-v2-Q2_K_L.ggufQ2KL31.03GBfalseUses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
Q2.5-MS-Mistoria-72b-v2-Q2_K.ggufQ2_K29.81GBfalseVery low quality but surprisingly usable.
Q2.5-MS-Mistoria-72b-v2-IQ2_M.ggufIQ2_M29.34GBfalseRelatively low quality, uses SOTA techniques to be surprisingly usable.
Q2.5-MS-Mistoria-72b-v2-IQ2_XS.ggufIQ2_XS27.06GBfalseLow quality, uses SOTA techniques to be usable.
Q2.5-MS-Mistoria-72b-v2-IQ2_XXS.ggufIQ2_XXS25.49GBfalseVery low quality, uses SOTA techniques to be usable.
Q2.5-MS-Mistoria-72b-v2-IQ1_M.ggufIQ1_M23.74GBfalseExtremely low quality, not recommended.

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.

Downloading using huggingface-cli

<details> <summary>Click to view download instructions</summary>

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/Q2.5-MS-Mistoria-72b-v2-GGUF --include "Q2.5-MS-Mistoria-72b-v2-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/Q2.5-MS-Mistoria-72b-v2-GGUF --include "Q2.5-MS-Mistoria-72b-v2-Q8_0/*" --local-dir ./

You can either specify a new local-dir (Q2.5-MS-Mistoria-72b-v2-Q8_0) or download them all in place (./)

</details>

Q40X_X information

<details> <summary>Click to view Q40X_X information</summary> These are NOT for Metal (Apple) or GPU (nvidia/AMD/intel) offloading, only ARM chips (and certain AVX2/AVX512 CPUs).

If you're using an ARM chip, the Q40XX quants will have a substantial speedup. Check out Q4044 speed comparisons on the original pull request

To check which one would work best for your ARM chip, you can check AArch64 SoC features (thanks EloyOn!).

If you're using a CPU that supports AVX2 or AVX512 (typically server CPUs and AMD's latest Zen5 CPUs) and are not offloading to a GPU, the Q408_8 may offer a nice speed as well:

<details> <summary>Click to view benchmarks on an AVX2 system (EPYC7702)</summary>

modelsizeparamsbackendthreadstestt/s% (vs Q4_0)
qwen2 3B Q4_01.70 GiB3.09 BCPU64pp512204.03 ± 1.03100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64pp1024282.92 ± 0.19100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64pp2048259.49 ± 0.44100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64tg12839.12 ± 0.27100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64tg25639.31 ± 0.69100%
qwen2 3B Q4_01.70 GiB3.09 BCPU64tg51240.52 ± 0.03100%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64pp512301.02 ± 1.74147%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64pp1024287.23 ± 0.20101%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64pp2048262.77 ± 1.81101%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64tg12818.80 ± 0.9948%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64tg25624.46 ± 3.0483%
qwen2 3B Q4KM1.79 GiB3.09 BCPU64tg51236.32 ± 3.5990%
qwen2 3B Q408_81.69 GiB3.09 BCPU64pp512271.71 ± 3.53133%
qwen2 3B Q408_81.69 GiB3.09 BCPU64pp1024279.86 ± 45.63100%
qwen2 3B Q408_81.69 GiB3.09 BCPU64pp2048320.77 ± 5.00124%
qwen2 3B Q408_81.69 GiB3.09 BCPU64tg12843.51 ± 0.05111%
qwen2 3B Q408_81.69 GiB3.09 BCPU64tg25643.35 ± 0.09110%
qwen2 3B Q408_81.69 GiB3.09 BCPU64tg51242.60 ± 0.31105%

Q408_8 offers a nice bump to prompt processing and a small bump to text generation

</details>

</details>

Which file should I choose?

<details> <summary>Click here for details</summary>

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.

</details>

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.

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