Arcee-Nova-GGUF / README.md
bartowski's picture
Update metadata with huggingface_hub
66d7fc4 verified
metadata
base_model: arcee-ai/Arcee-Nova
license: other
pipeline_tag: text-generation
quantized_by: bartowski

Llamacpp imatrix Quantizations of Arcee-Nova

Using llama.cpp release b3389 for quantization.

Original model: https://huggingface.co/arcee-ai/Arcee-Nova

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
Arcee-Nova-f32.gguf f32 290.83GB true Full F32 weights.
Arcee-Nova-Q8_0.gguf Q8_0 77.26GB true Extremely high quality, generally unneeded but max available quant.
Arcee-Nova-Q6_K_L.gguf Q6_K_L 64.95GB true Uses Q8_0 for embed and output weights. Very high quality, near perfect, recommended.
Arcee-Nova-Q6_K.gguf Q6_K 64.35GB true Very high quality, near perfect, recommended.
Arcee-Nova-Q5_K_L.gguf Q5_K_L 55.22GB true Uses Q8_0 for embed and output weights. High quality, recommended.
Arcee-Nova-Q5_K_M.gguf Q5_K_M 54.45GB true High quality, recommended.
Arcee-Nova-Q5_K_S.gguf Q5_K_S 51.38GB true High quality, recommended.
Arcee-Nova-Q4_K_L.gguf Q4_K_L 48.34GB false Uses Q8_0 for embed and output weights. Good quality, recommended.
Arcee-Nova-Q4_K_M.gguf Q4_K_M 47.42GB false Good quality, default size for must use cases, recommended.
Arcee-Nova-Q4_K_S.gguf Q4_K_S 43.89GB false Slightly lower quality with more space savings, recommended.
Arcee-Nova-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.
Arcee-Nova-IQ4_XS.gguf IQ4_XS 39.71GB false Decent quality, smaller than Q4_K_S with similar performance, recommended.
Arcee-Nova-Q3_K_L.gguf Q3_K_L 39.51GB false Lower quality but usable, good for low RAM availability.
Arcee-Nova-Q3_K_M.gguf Q3_K_M 37.70GB false Low quality.
Arcee-Nova-IQ3_M.gguf IQ3_M 35.50GB false Medium-low quality, new method with decent performance comparable to Q3_K_M.
Arcee-Nova-Q3_K_S.gguf Q3_K_S 34.49GB false Low quality, not recommended.
Arcee-Nova-IQ3_XS.gguf IQ3_XS 32.84GB false Lower quality, new method with decent performance, slightly better than Q3_K_S.
Arcee-Nova-Q2_K_L.gguf Q2_K_L 31.03GB false Uses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
Arcee-Nova-Q2_K.gguf Q2_K 29.81GB false Very low quality but surprisingly usable.
Arcee-Nova-IQ2_M.gguf IQ2_M 29.34GB false Relatively low quality, uses SOTA techniques to be surprisingly usable.

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

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/Arcee-Nova-GGUF --include "Arcee-Nova-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/Arcee-Nova-GGUF --include "Arcee-Nova-Q8_0.gguf/*" --local-dir Arcee-Nova-Q8_0

You can either specify a new local-dir (Arcee-Nova-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