bartowski's picture
Update metadata with huggingface_hub
06216c2 verified
metadata
base_model: EVA-UNIT-01/EVA-Qwen2.5-72B-v0.0
datasets:
  - anthracite-org/kalo-opus-instruct-22k-no-refusal
  - Nopm/Opus_WritingStruct
  - Gryphe/Sonnet3.5-SlimOrcaDedupCleaned
  - Gryphe/Sonnet3.5-Charcard-Roleplay
  - Gryphe/ChatGPT-4o-Writing-Prompts
  - Epiculous/Synthstruct-Gens-v1.1-Filtered-n-Cleaned
  - Epiculous/SynthRP-Gens-v1.1-Filtered-n-Cleaned
  - nothingiisreal/Reddit-Dirty-And-WritingPrompts
  - allura-org/Celeste-1.x-data-mixture
license: other
license_name: qwen
license_link: https://huggingface.co/Qwen/Qwen2.5-72B-Instruct/blob/main/LICENSE
pipeline_tag: text-generation
tags:
  - generated_from_trainer
quantized_by: bartowski
model-index:
  - name: EVA-Qwen2.5-72B-SFFT-v0.0
    results: []

Llamacpp imatrix Quantizations of EVA-Qwen2.5-72B-v0.0

Using llama.cpp release b3972 for quantization.

Original model: https://huggingface.co/EVA-UNIT-01/EVA-Qwen2.5-72B-v0.0

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:

Filename Quant type File Size Split Description
EVA-Qwen2.5-72B-v0.0-Q8_0.gguf Q8_0 77.26GB true Extremely high quality, generally unneeded but max available quant.
EVA-Qwen2.5-72B-v0.0-Q6_K.gguf Q6_K 64.35GB true Very high quality, near perfect, recommended.
EVA-Qwen2.5-72B-v0.0-Q5_K_M.gguf Q5_K_M 54.45GB true High quality, recommended.
EVA-Qwen2.5-72B-v0.0-Q5_K_S.gguf Q5_K_S 51.38GB true High quality, recommended.
EVA-Qwen2.5-72B-v0.0-Q4_K_M.gguf Q4_K_M 47.42GB false Good quality, default size for must use cases, recommended.
EVA-Qwen2.5-72B-v0.0-Q4_K_S.gguf Q4_K_S 43.89GB false Slightly lower quality with more space savings, recommended.
EVA-Qwen2.5-72B-v0.0-Q4_0.gguf Q4_0 41.38GB false Legacy format, generally not worth using over similarly sized formats
EVA-Qwen2.5-72B-v0.0-Q3_K_XL.gguf Q3_K_XL 40.60GB false Uses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability.
EVA-Qwen2.5-72B-v0.0-IQ4_XS.gguf IQ4_XS 39.71GB false Decent quality, smaller than Q4_K_S with similar performance, recommended.
EVA-Qwen2.5-72B-v0.0-Q3_K_L.gguf Q3_K_L 39.51GB false Lower quality but usable, good for low RAM availability.
EVA-Qwen2.5-72B-v0.0-Q3_K_M.gguf Q3_K_M 37.70GB false Low quality.
EVA-Qwen2.5-72B-v0.0-IQ3_M.gguf IQ3_M 35.50GB false Medium-low quality, new method with decent performance comparable to Q3_K_M.
EVA-Qwen2.5-72B-v0.0-Q3_K_S.gguf Q3_K_S 34.49GB false Low quality, not recommended.
EVA-Qwen2.5-72B-v0.0-IQ3_XXS.gguf IQ3_XXS 31.85GB false Lower quality, new method with decent performance, comparable to Q3 quants.
EVA-Qwen2.5-72B-v0.0-Q2_K_L.gguf Q2_K_L 31.03GB false Uses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
EVA-Qwen2.5-72B-v0.0-Q2_K.gguf Q2_K 29.81GB false Very low quality but surprisingly usable.
EVA-Qwen2.5-72B-v0.0-IQ2_M.gguf IQ2_M 29.34GB false Relatively low quality, uses SOTA techniques to be surprisingly usable.
EVA-Qwen2.5-72B-v0.0-IQ2_XS.gguf IQ2_XS 27.06GB false Low quality, uses SOTA techniques to be usable.
EVA-Qwen2.5-72B-v0.0-IQ2_XXS.gguf IQ2_XXS 25.49GB false Very low quality, uses SOTA techniques to be usable.
EVA-Qwen2.5-72B-v0.0-IQ1_M.gguf IQ1_M 23.74GB false Extremely low quality, not recommended.

Embed/output weights

Some of these quants (Q3_K_XL, Q4_K_L 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!

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/EVA-Qwen2.5-72B-v0.0-GGUF --include "EVA-Qwen2.5-72B-v0.0-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/EVA-Qwen2.5-72B-v0.0-GGUF --include "EVA-Qwen2.5-72B-v0.0-Q8_0/*" --local-dir ./

You can either specify a new local-dir (EVA-Qwen2.5-72B-v0.0-Q8_0) or download them all in place (./)

Q4_0_X_X

These are NOT for Metal (Apple) offloading, only ARM chips.

If you're using an ARM chip, the Q4_0_X_X quants will have a substantial speedup. Check out Q4_0_4_4 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!).

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.

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