Model Overview
Model Features
Model Capabilities
Use Cases
🚀 Llamacpp imatrix Quantizations of Valkyrie-49B-v1 by TheDrummer
This project provides quantized versions of the Valkyrie-49B-v1 model using the llama.cpp library. It offers various quantization types to meet different performance and storage requirements.
Metadata
Property | Details |
---|---|
Quantized By | bartowski |
Pipeline Tag | text-generation |
Base Model | TheDrummer/Valkyrie-49B-v1 |
Base Model Relation | quantized |
🚀 Quick Start
Quantization Details
We used llama.cpp release b5415 for quantization. The original model can be found at https://huggingface.co/TheDrummer/Valkyrie-49B-v1. All quantizations were made using the imatrix option with the dataset from here.
Running the Model
- Using LM Studio: You can run the quantized models in LM Studio.
- Using llama.cpp: You can also run them directly with llama.cpp or any other llama.cpp - based project.
✨ Features
Prompt Format
<|begin_of_text|><|start_header_id|>system<|end_header_id|>
{system_prompt}<|eot_id|><|start_header_id|>user<|end_header_id|>
{prompt}<|eot_id|><|start_header_id|>assistant<|end_header_id|>
Download Options
You can download a specific file (not the whole branch) from the following table:
Filename | Quant type | File Size | Split | Description |
---|---|---|---|---|
Valkyrie-49B-v1-bf16.gguf | bf16 | 99.74GB | true | Full BF16 weights. |
Valkyrie-49B-v1-Q8_0.gguf | Q8_0 | 52.99GB | true | Extremely high quality, generally unneeded but max available quant. |
Valkyrie-49B-v1-Q6_K_L.gguf | Q6_K_L | 41.43GB | false | Uses Q8_0 for embed and output weights. Very high quality, near perfect, recommended. |
Valkyrie-49B-v1-Q6_K.gguf | Q6_K | 40.92GB | false | Very high quality, near perfect, recommended. |
Valkyrie-49B-v1-Q5_K_L.gguf | Q5_K_L | 36.04GB | false | Uses Q8_0 for embed and output weights. High quality, recommended. |
Valkyrie-49B-v1-Q5_K_M.gguf | Q5_K_M | 35.39GB | false | High quality, recommended. |
Valkyrie-49B-v1-Q5_K_S.gguf | Q5_K_S | 34.43GB | false | High quality, recommended. |
Valkyrie-49B-v1-Q4_1.gguf | Q4_1 | 31.38GB | false | Legacy format, similar performance to Q4_K_S but with improved tokens/watt on Apple silicon. |
Valkyrie-49B-v1-Q4_K_L.gguf | Q4_K_L | 31.00GB | false | Uses Q8_0 for embed and output weights. Good quality, recommended. |
Valkyrie-49B-v1-Q4_K_M.gguf | Q4_K_M | 30.22GB | false | Good quality, default size for most use cases, recommended. |
Valkyrie-49B-v1-Q4_K_S.gguf | Q4_K_S | 28.63GB | false | Slightly lower quality with more space savings, recommended. |
Valkyrie-49B-v1-Q4_0.gguf | Q4_0 | 28.46GB | false | Legacy format, offers online repacking for ARM and AVX CPU inference. |
Valkyrie-49B-v1-IQ4_NL.gguf | IQ4_NL | 28.38GB | false | Similar to IQ4_XS, but slightly larger. Offers online repacking for ARM CPU inference. |
Valkyrie-49B-v1-Q3_K_XL.gguf | Q3_K_XL | 27.19GB | false | Uses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability. |
Valkyrie-49B-v1-IQ4_XS.gguf | IQ4_XS | 26.87GB | false | Decent quality, smaller than Q4_K_S with similar performance, recommended. |
Valkyrie-49B-v1-Q3_K_L.gguf | Q3_K_L | 26.27GB | false | Lower quality but usable, good for low RAM availability. |
Valkyrie-49B-v1-Q3_K_M.gguf | Q3_K_M | 24.31GB | false | Low quality. |
Valkyrie-49B-v1-IQ3_M.gguf | IQ3_M | 22.66GB | false | Medium-low quality, new method with decent performance comparable to Q3_K_M. |
Valkyrie-49B-v1-Q3_K_S.gguf | Q3_K_S | 21.96GB | false | Low quality, not recommended. |
Valkyrie-49B-v1-IQ3_XS.gguf | IQ3_XS | 20.91GB | false | Lower quality, new method with decent performance, slightly better than Q3_K_S. |
Valkyrie-49B-v1-Q2_K_L.gguf | Q2_K_L | 19.77GB | false | Uses Q8_0 for embed and output weights. Very low quality but surprisingly usable. |
Valkyrie-49B-v1-IQ3_XXS.gguf | IQ3_XXS | 19.52GB | false | Lower quality, new method with decent performance, comparable to Q3 quants. |
Valkyrie-49B-v1-Q2_K.gguf | Q2_K | 18.74GB | false | Very low quality but surprisingly usable. |
Valkyrie-49B-v1-IQ2_M.gguf | IQ2_M | 17.16GB | false | Relatively low quality, uses SOTA techniques to be surprisingly usable. |
Valkyrie-49B-v1-IQ2_S.gguf | IQ2_S | 15.85GB | false | Low quality, uses SOTA techniques to be usable. |
Valkyrie-49B-v1-IQ2_XS.gguf | IQ2_XS | 15.08GB | false | Low quality, uses SOTA techniques to be usable. |
Valkyrie-49B-v1-IQ2_XXS.gguf | IQ2_XXS | 13.66GB | false | Very low quality, uses SOTA techniques to be usable. |
Embed/Output Weights
Some of these quantizations (Q3_K_XL, Q4_K_L etc) are the standard quantization method with the embeddings and output weights quantized to Q8_0 instead of what they would normally default to.
📦 Installation
Downloading using huggingface-cli
Click to view download instructions
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/TheDrummer_Valkyrie-49B-v1-GGUF --include "TheDrummer_Valkyrie-49B-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/TheDrummer_Valkyrie-49B-v1-GGUF --include "TheDrummer_Valkyrie-49B-v1-Q8_0/*" --local-dir ./
You can either specify a new local - dir (TheDrummer_Valkyrie-49B-v1-Q8_0) or download them all in place (./)
🔧 Technical Details
ARM/AVX Information
Previously, you would download Q4_0_4_4/4_8/8_8, and these would have their weights interleaved in memory in order to improve performance on ARM and AVX machines by loading up more data in one pass.
Now, however, there is something called "online repacking" for weights. details in this PR. If you use Q4_0 and your hardware would benefit from repacking weights, it will do it automatically on the fly.
As of llama.cpp build b4282 you will not be able to run the Q4_0_X_X files and will instead need to use Q4_0.
Additionally, if you want to get slightly better quality, you can use IQ4_NL thanks to this PR which will also repack the weights for ARM, though only the 4_4 for now. The loading time may be slower but it will result in an overall speed increase.
Click to view Q4_0_X_X information (deprecated)
I'm keeping this section to show the potential theoretical uplift in performance from using the Q4_0 with online repacking.
Click to view benchmarks on an AVX2 system (EPYC7702)
model | size | params | backend | threads | test | t/s | % (vs Q4_0) |
---|---|---|---|---|---|---|---|
qwen2 3B Q4_0 | 1.70 GiB | 3.09 B | CPU | 64 | pp512 | 204.03 ± 1.03 | 100% |
qwen2 3B Q4_0 | 1.70 GiB | 3.09 B | CPU | 64 | pp1024 | 282.92 ± 0.19 | 100% |
qwen2 3B Q4_0 | 1.70 GiB | 3.09 B | CPU | 64 | pp2048 | 259.49 ± 0.44 | 100% |
qwen2 3B Q4_0 | 1.70 GiB | 3.09 B | CPU | 64 | tg128 | 39.12 ± 0.27 | 100% |
qwen2 3B Q4_0 | 1.70 GiB | 3.09 B | CPU | 64 | tg256 | 39.31 ± 0.69 | 100% |
qwen2 3B Q4_0 | 1.70 GiB | 3.09 B | CPU | 64 | tg512 | 40.52 ± 0.03 | 100% |
qwen2 3B Q4_K_M | 1.79 GiB | 3.09 B | CPU | 64 | pp512 | 301.02 ± 1.74 | 147% |
qwen2 3B Q4_K_M | 1.79 GiB | 3.09 B | CPU | 64 | pp1024 | 287.23 ± 0.20 | 101% |
qwen2 3B Q4_K_M | 1.79 GiB | 3.09 B | CPU | 64 | pp2048 | 262.77 ± 1.81 | 101% |
qwen2 3B Q4_K_M | 1.79 GiB | 3.09 B | CPU | 64 | tg128 | 18.80 ± 0.99 | 48% |
qwen2 3B Q4_K_M | 1.79 GiB | 3.09 B | CPU | 64 | tg256 | 24.46 ± 3.04 | 83% |
qwen2 3B Q4_K_M | 1.79 GiB | 3.09 B | CPU | 64 | tg512 | 36.32 ± 3.59 | 90% |
qwen2 3B Q4_0_8_8 | 1.69 GiB | 3.09 B | CPU | 64 | pp512 | 271.71 ± 3.53 | 133% |
qwen2 3B Q4_0_8_8 | 1.69 GiB | 3.09 B | CPU | 64 | pp1024 | 279.86 ± 45.63 | 100% |
qwen2 3B Q4_0_8_8 | 1.69 GiB | 3.09 B | CPU | 64 | pp2048 | 320.77 ± 5.00 | 124% |
qwen2 3B Q4_0_8_8 | 1.69 GiB | 3.09 B | CPU | 64 | tg128 | 43.51 ± 0.05 | 111% |
qwen2 3B Q4_0_8_8 | 1.69 GiB | 3.09 B | CPU | 64 | tg256 | 43.35 ± 0.09 | 110% |
qwen2 3B Q4_0_8_8 | 1.69 GiB | 3.09 B | CPU | 64 | tg512 | 42.60 ± 0.31 | 105% |
Q4_0_8_8 offers a nice bump to prompt processing and a small bump to text generation
📚 Documentation
Which file should I choose?
Click here for details
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... (The original text seems incomplete here, but we keep it as it is.)

