extra_gated_heading: Acknowledge to follow corresponding license to access the repository
extra_gated_button_content: Agree and access repository
extra_gated_fields:
First Name: text
Last Name: text
Country: country
Affiliation: text
license: cc-by-nc-4.0
datasets:
- Salesforce/xlam-function-calling-60k
language:
- en
pipeline_tag: text-generation
tags:
- function-calling
- LLM Agent
- tool-use
- mistral
- pytorch
quantized_by: bartowski
Llamacpp Static (no imatrix) Quantizations of xLAM-7b-r
Using llama.cpp release b3634 for quantization.
Original model: https://huggingface.co/Salesforce/xLAM-7b-r
Prompt format
No prompt format
Download a file (not the whole branch) from below:
| Filename | Quant type | File Size | Description |
|---|---|---|---|
| xLAM-7b-r-Q8_0.gguf | Q8_0 | 7.69GB | Extremely high quality, generally unneeded but max available quant. |
| xLAM-7b-r-Q6_K.gguf | Q6_K | 5.94GB | Very high quality, near perfect, recommended. |
| xLAM-7b-r-Q5_K_M.gguf | Q5_K_M | High quality, recommended. | |
| xLAM-7b-r-Q4_K_M.gguf | Q4_K_M | 4.36GB | Good quality, uses about 4.83 bits per weight, recommended. |
| xLAM-7b-r-IQ4_NL.gguf | IQ4_NL | Decent quality, slightly smaller than Q4_K_S with similar performance recommended. | |
| xLAM-7b-r-Q3_K_L.gguf | Q3_K_L | Lower quality but usable, good for low RAM availability. | |
| xLAM-7b-r-Q2_K.gguf | Q2_K | Very low quality but surprisingly usable. |
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