Llamacpp Quantizations of wavecoder-ultra-6.7b
Using llama.cpp release b2675 for quantization.
Original model: https://huggingface.co/microsoft/wavecoder-ultra-6.7b
All quants made using imatrix option with dataset provided by Kalomaze here
Prompt format
This seems to follow the DeepSeek coder format, aka Alpaca.
{system_prompt}
### Instruction: {prompt}
### Response:
Download a file (not the whole branch) from below:
| Filename | Quant type | File Size | Description |
|---|---|---|---|
| wavecoder-ultra-6.7b-Q8_0.gguf | Q8_0 | 7.16GB | Extremely high quality, generally unneeded but max available quant. |
| wavecoder-ultra-6.7b-Q6_K.gguf | Q6_K | 5.52GB | Very high quality, near perfect, recommended. |
| wavecoder-ultra-6.7b-Q5_K_M.gguf | Q5_K_M | 4.78GB | High quality, recommended. |
| wavecoder-ultra-6.7b-Q5_K_S.gguf | Q5_K_S | 4.65GB | High quality, recommended. |
| wavecoder-ultra-6.7b-Q4_K_M.gguf | Q4_K_M | 4.08GB | Good quality, uses about 4.83 bits per weight, recommended. |
| wavecoder-ultra-6.7b-Q4_K_S.gguf | Q4_K_S | 3.85GB | Slightly lower quality with more space savings, recommended. |
| wavecoder-ultra-6.7b-IQ4_NL.gguf | IQ4_NL | 3.82GB | Decent quality, slightly smaller than Q4_K_S with similar performance recommended. |
| wavecoder-ultra-6.7b-IQ4_XS.gguf | IQ4_XS | 3.62GB | Decent quality, smaller than Q4_K_S with similar performance, recommended. |
| wavecoder-ultra-6.7b-Q3_K_L.gguf | Q3_K_L | 3.59GB | Lower quality but usable, good for low RAM availability. |
| wavecoder-ultra-6.7b-Q3_K_M.gguf | Q3_K_M | 3.29GB | Even lower quality. |
| wavecoder-ultra-6.7b-IQ3_M.gguf | IQ3_M | 3.11GB | Medium-low quality, new method with decent performance comparable to Q3_K_M. |
| wavecoder-ultra-6.7b-IQ3_S.gguf | IQ3_S | 2.94GB | Lower quality, new method with decent performance, recommended over Q3_K_S quant, same size with better performance. |
| wavecoder-ultra-6.7b-Q3_K_S.gguf | Q3_K_S | 2.94GB | Low quality, not recommended. |
| wavecoder-ultra-6.7b-IQ3_XS.gguf | IQ3_XS | 2.79GB | Lower quality, new method with decent performance, slightly better than Q3_K_S. |
| wavecoder-ultra-6.7b-IQ3_XXS.gguf | IQ3_XXS | 2.58GB | Lower quality, new method with decent performance, comparable to Q3 quants. |
| wavecoder-ultra-6.7b-Q2_K.gguf | Q2_K | 2.53GB | Very low quality but surprisingly usable. |
| wavecoder-ultra-6.7b-IQ2_M.gguf | IQ2_M | 2.36GB | Very low quality, uses SOTA techniques to also be surprisingly usable. |
| wavecoder-ultra-6.7b-IQ2_S.gguf | IQ2_S | 2.19GB | Very low quality, uses SOTA techniques to be usable. |
| wavecoder-ultra-6.7b-IQ2_XS.gguf | IQ2_XS | 2.03GB | Very low quality, uses SOTA techniques to be usable. |
| wavecoder-ultra-6.7b-IQ2_XXS.gguf | IQ2_XXS | 1.85GB | Lower quality, uses SOTA techniques to be usable. |
| wavecoder-ultra-6.7b-IQ1_M.gguf | IQ1_M | 1.65GB | Extremely low quality, not recommended. |
| wavecoder-ultra-6.7b-IQ1_S.gguf | IQ1_S | 1.52GB | 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:
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