bartowski's picture
Llamacpp quants
e100dde verified
|
raw
history blame
8.04 kB
metadata
license: other
base_model: meta-llama/Meta-Llama-3-8B
tags:
  - generated_from_trainer
  - axolotl
model-index:
  - name: out
    results: []
datasets:
  - cognitivecomputations/Dolphin-2.9
  - teknium/OpenHermes-2.5
  - m-a-p/CodeFeedback-Filtered-Instruction
  - cognitivecomputations/dolphin-coder
  - cognitivecomputations/samantha-data
  - HuggingFaceH4/ultrachat_200k
  - microsoft/orca-math-word-problems-200k
  - abacusai/SystemChat-1.1
  - Locutusque/function-calling-chatml
  - internlm/Agent-FLAN
quantized_by: bartowski
pipeline_tag: text-generation

Llamacpp imatrix Quantizations of dolphin-2.9-llama3-8b

Using llama.cpp release b2777 for quantization.

Original model: https://huggingface.co/cognitivecomputations/dolphin-2.9-llama3-8b

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

Prompt format

<|im_start|>system
You are Dolphin, a helpful AI assistant.<|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
dolphin-2.9-llama3-8b-Q8_0.gguf Q8_0 8.54GB Extremely high quality, generally unneeded but max available quant.
dolphin-2.9-llama3-8b-Q6_K.gguf Q6_K 6.59GB Very high quality, near perfect, recommended.
dolphin-2.9-llama3-8b-Q5_K_M.gguf Q5_K_M 5.73GB High quality, recommended.
dolphin-2.9-llama3-8b-Q5_K_S.gguf Q5_K_S 5.59GB High quality, recommended.
dolphin-2.9-llama3-8b-Q4_K_M.gguf Q4_K_M 4.92GB Good quality, uses about 4.83 bits per weight, recommended.
dolphin-2.9-llama3-8b-Q4_K_S.gguf Q4_K_S 4.69GB Slightly lower quality with more space savings, recommended.
dolphin-2.9-llama3-8b-IQ4_NL.gguf IQ4_NL 4.67GB Decent quality, slightly smaller than Q4_K_S with similar performance recommended.
dolphin-2.9-llama3-8b-IQ4_XS.gguf IQ4_XS 4.44GB Decent quality, smaller than Q4_K_S with similar performance, recommended.
dolphin-2.9-llama3-8b-Q3_K_L.gguf Q3_K_L 4.32GB Lower quality but usable, good for low RAM availability.
dolphin-2.9-llama3-8b-Q3_K_M.gguf Q3_K_M 4.01GB Even lower quality.
dolphin-2.9-llama3-8b-IQ3_M.gguf IQ3_M 3.78GB Medium-low quality, new method with decent performance comparable to Q3_K_M.
dolphin-2.9-llama3-8b-IQ3_S.gguf IQ3_S 3.68GB Lower quality, new method with decent performance, recommended over Q3_K_S quant, same size with better performance.
dolphin-2.9-llama3-8b-Q3_K_S.gguf Q3_K_S 3.66GB Low quality, not recommended.
dolphin-2.9-llama3-8b-IQ3_XS.gguf IQ3_XS 3.51GB Lower quality, new method with decent performance, slightly better than Q3_K_S.
dolphin-2.9-llama3-8b-IQ3_XXS.gguf IQ3_XXS 3.27GB Lower quality, new method with decent performance, comparable to Q3 quants.
dolphin-2.9-llama3-8b-Q2_K.gguf Q2_K 3.17GB Very low quality but surprisingly usable.
dolphin-2.9-llama3-8b-IQ2_M.gguf IQ2_M 2.94GB Very low quality, uses SOTA techniques to also be surprisingly usable.
dolphin-2.9-llama3-8b-IQ2_S.gguf IQ2_S 2.75GB Very low quality, uses SOTA techniques to be usable.
dolphin-2.9-llama3-8b-IQ2_XS.gguf IQ2_XS 2.60GB Very low quality, uses SOTA techniques to be usable.
dolphin-2.9-llama3-8b-IQ2_XXS.gguf IQ2_XXS 2.39GB Lower quality, uses SOTA techniques to be usable.
dolphin-2.9-llama3-8b-IQ1_M.gguf IQ1_M 2.16GB Extremely low quality, not recommended.
dolphin-2.9-llama3-8b-IQ1_S.gguf IQ1_S 2.01GB Extremely low quality, not recommended.

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