bartowski/airoboros-dpo-70b-3.3-GGUF

Llamacpp imatrix Quantizations of airoboros-dpo-70b-3.3

Using llama.cpp release b2854 for quantization.

Original model: https://huggingface.co/jondurbin/airoboros-dpo-70b-3.3

All quants made using imatrix option with dataset provided by Kalomaze here

Prompt format

<|begin_of_text|><|start_header_id|>system<|end_header_id|>

{system_prompt}<|eot_id|><|start_header_id|>user<|end_header_id|>

{prompt}<|eot_id|><|start_header_id|>assistant<|end_header_id|>

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

Filename	Quant type	File Size	Description
airoboros-dpo-70b-3.3-Q8_0.gguf	Q8_0	74.97GB	Extremely high quality, generally unneeded but max available quant.
airoboros-dpo-70b-3.3-Q6_K.gguf	Q6_K	57.88GB	Very high quality, near perfect, recommended.
airoboros-dpo-70b-3.3-Q5_K_M.gguf	Q5_K_M	49.94GB	High quality, recommended.
airoboros-dpo-70b-3.3-Q5_K_S.gguf	Q5_K_S	48.65GB	High quality, recommended.
airoboros-dpo-70b-3.3-Q4_K_M.gguf	Q4_K_M	42.52GB	Good quality, uses about 4.83 bits per weight, recommended.
airoboros-dpo-70b-3.3-Q4_K_S.gguf	Q4_K_S	40.34GB	Slightly lower quality with more space savings, recommended.
airoboros-dpo-70b-3.3-IQ4_NL.gguf	IQ4_NL	40.05GB	Decent quality, slightly smaller than Q4_K_S with similar performance recommended.
airoboros-dpo-70b-3.3-IQ4_XS.gguf	IQ4_XS	37.90GB	Decent quality, smaller than Q4_K_S with similar performance, recommended.
airoboros-dpo-70b-3.3-Q3_K_L.gguf	Q3_K_L	37.14GB	Lower quality but usable, good for low RAM availability.
airoboros-dpo-70b-3.3-Q3_K_M.gguf	Q3_K_M	34.26GB	Even lower quality.
airoboros-dpo-70b-3.3-IQ3_M.gguf	IQ3_M	31.93GB	Medium-low quality, new method with decent performance comparable to Q3_K_M.
airoboros-dpo-70b-3.3-IQ3_S.gguf	IQ3_S	30.91GB	Lower quality, new method with decent performance, recommended over Q3_K_S quant, same size with better performance.
airoboros-dpo-70b-3.3-Q3_K_S.gguf	Q3_K_S	30.91GB	Low quality, not recommended.
airoboros-dpo-70b-3.3-IQ3_XS.gguf	IQ3_XS	29.30GB	Lower quality, new method with decent performance, slightly better than Q3_K_S.
airoboros-dpo-70b-3.3-IQ3_XXS.gguf	IQ3_XXS	27.46GB	Lower quality, new method with decent performance, comparable to Q3 quants.
airoboros-dpo-70b-3.3-Q2_K.gguf	Q2_K	26.37GB	Very low quality but surprisingly usable.
airoboros-dpo-70b-3.3-IQ2_M.gguf	IQ2_M	24.11GB	Very low quality, uses SOTA techniques to also be surprisingly usable.
airoboros-dpo-70b-3.3-IQ2_S.gguf	IQ2_S	22.24GB	Very low quality, uses SOTA techniques to be usable.
airoboros-dpo-70b-3.3-IQ2_XS.gguf	IQ2_XS	21.14GB	Very low quality, uses SOTA techniques to be usable.
airoboros-dpo-70b-3.3-IQ2_XXS.gguf	IQ2_XXS	19.09GB	Lower quality, uses SOTA techniques to be usable.
airoboros-dpo-70b-3.3-IQ1_M.gguf	IQ1_M	16.75GB	Extremely low quality, not recommended.
airoboros-dpo-70b-3.3-IQ1_S.gguf	IQ1_S	15.34GB	Extremely low quality, not recommended.

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/airoboros-dpo-70b-3.3-GGUF --include "airoboros-dpo-70b-3.3-Q4_K_M.gguf" --local-dir ./ --local-dir-use-symlinks False

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/airoboros-dpo-70b-3.3-GGUF --include "airoboros-dpo-70b-3.3-Q8_0.gguf/*" --local-dir airoboros-dpo-70b-3.3-Q8_0 --local-dir-use-symlinks False

You can either specify a new local-dir (airoboros-dpo-70b-3.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