Downloads · 30 days
20
5% of all-time downloads
jodog0412/gemma-2-27b-it-Q4_K_M
gemma-2-27b-it-Q4_K_M is a text generation model from jodog0412. Use it when you need the model to write or continue text. It is set up for transformers. The card lists the license as gemma.
Using <a href="https://github.com/ggerganov/llama.cpp/"llama.cpp</a for quantization.
Downloads · 30 days
20
5% of all-time downloads
All-time downloads
438
Public
Repo size
16.6 GB
Likes
0
Public
Click a slice to open those files.
.gguf16.6 GB · 100%
From the Hugging Face model README
Using <a href="https://github.com/ggerganov/llama.cpp/">llama.cpp</a> for quantization.
Original model: https://huggingface.co/google/gemma-2-27b-it
Thank you <a hreft="https://huggingface.co/bartowski"> bartowski</a> for inspiration to quantize the model.
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 jodog0412/gemma-2-27b-it-Q4_K_M --include "gemma-2-instruct-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 jodog0412/gemma-2-27b-it-Q4_K_M --include "gemma-2-instruct-Q4_K_M.gguf/*" --local-dir gemma-2-instruct-Q4_K_M
You can either specify a new local-dir (gemma-2-instruct-Q4_K_M) or download them all in place (./)
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