bartowski/Tiger-Gemma-9B-v1-GGUF

Llamacpp imatrix Quantizations of Tiger-Gemma-9B-v1

Using llama.cpp release b3389 for quantization.

Original model: https://huggingface.co/TheDrummer/Tiger-Gemma-9B-v1

All quants made using imatrix option with dataset from here

Prompt format

<bos><start_of_turn>user
{prompt}<end_of_turn>
<start_of_turn>model
<end_of_turn>
<start_of_turn>model

Note that this model does not support a System prompt.

Download a file (not the whole branch) from below:

Filename	Quant type	File Size	Split	Description
Tiger-Gemma-9B-v1-f32.gguf	f32	36.97GB	false	Full F32 weights.
Tiger-Gemma-9B-v1-Q8_0.gguf	Q8_0	9.83GB	false	Extremely high quality, generally unneeded but max available quant.
Tiger-Gemma-9B-v1-Q6_K_L.gguf	Q6_K_L	7.81GB	false	Uses Q8_0 for embed and output weights. Very high quality, near perfect, recommended.
Tiger-Gemma-9B-v1-Q6_K.gguf	Q6_K	7.59GB	false	Very high quality, near perfect, recommended.
Tiger-Gemma-9B-v1-Q5_K_L.gguf	Q5_K_L	6.87GB	false	Uses Q8_0 for embed and output weights. High quality, recommended.
Tiger-Gemma-9B-v1-Q5_K_M.gguf	Q5_K_M	6.65GB	false	High quality, recommended.
Tiger-Gemma-9B-v1-Q5_K_S.gguf	Q5_K_S	6.48GB	false	High quality, recommended.
Tiger-Gemma-9B-v1-Q4_K_L.gguf	Q4_K_L	5.98GB	false	Uses Q8_0 for embed and output weights. Good quality, recommended.
Tiger-Gemma-9B-v1-Q4_K_M.gguf	Q4_K_M	5.76GB	false	Good quality, default size for must use cases, recommended.
Tiger-Gemma-9B-v1-Q4_K_S.gguf	Q4_K_S	5.48GB	false	Slightly lower quality with more space savings, recommended.
Tiger-Gemma-9B-v1-Q3_K_XL.gguf	Q3_K_XL	5.35GB	false	Uses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability.
Tiger-Gemma-9B-v1-IQ4_XS.gguf	IQ4_XS	5.18GB	false	Decent quality, smaller than Q4_K_S with similar performance, recommended.
Tiger-Gemma-9B-v1-Q3_K_L.gguf	Q3_K_L	5.13GB	false	Lower quality but usable, good for low RAM availability.
Tiger-Gemma-9B-v1-Q3_K_M.gguf	Q3_K_M	4.76GB	false	Low quality.
Tiger-Gemma-9B-v1-IQ3_M.gguf	IQ3_M	4.49GB	false	Medium-low quality, new method with decent performance comparable to Q3_K_M.
Tiger-Gemma-9B-v1-Q3_K_S.gguf	Q3_K_S	4.34GB	false	Low quality, not recommended.
Tiger-Gemma-9B-v1-IQ3_XS.gguf	IQ3_XS	4.14GB	false	Lower quality, new method with decent performance, slightly better than Q3_K_S.
Tiger-Gemma-9B-v1-Q2_K_L.gguf	Q2_K_L	4.03GB	false	Uses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
Tiger-Gemma-9B-v1-Q2_K.gguf	Q2_K	3.81GB	false	Very low quality but surprisingly usable.
Tiger-Gemma-9B-v1-IQ2_M.gguf	IQ2_M	3.43GB	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/Tiger-Gemma-9B-v1-GGUF --include "Tiger-Gemma-9B-v1-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/Tiger-Gemma-9B-v1-GGUF --include "Tiger-Gemma-9B-v1-Q8_0.gguf/*" --local-dir Tiger-Gemma-9B-v1-Q8_0

You can either specify a new local-dir (Tiger-Gemma-9B-v1-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