Behemoth ReduX 123B v1.1 needs about 76.7 GB of memory at Q4_K_M (a 73.2 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 27 quants, from 0.0 GB to 130.3 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 11.8 GB.
Behemoth ReduX 123B v1.1 – 123 billion‑parameter creative Llama model
Behemoth ReduX 123B v1.1 is a 123 billion‑parameter Llama model tuned for creative text generation. It supports a 131 072‑token context window and includes a tools ability. The model is available in multiple GGUF quantizations.
Good at
- Creative writing
- Tool‑based interactions
- Long‑form context
Limits
- Large memory footprint for higher quants
- No vision support
- License not specified
Best for
- Writing fiction
- Generating code snippets
- Chatbot dialogue
Who it’s for. Developers and content creators who need a large model for creative tasks and can allocate sufficient GPU memory. The model is suitable for users comfortable with llama.cpp or similar inference engines.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 3.5 GB | Fits | Get file → | |
| IQ1_S | 26.0 GB | 29.4 GB | Too big | Get file → | |
| IQ1_M | 28.4 GB | 31.8 GB | Too big | Get file → | |
| IQ2_XXS | 32.4 GB | 35.9 GB | Too big | Get file → | |
| IQ2_XS | 36.1 GB | 39.5 GB | Too big | Get file → | |
| IQ2_S | 38.4 GB | 41.8 GB | Too big | Get file → | |
| IQ2_M | 41.6 GB | 45.1 GB | Too big | Get file → | |
| Q2_K | 45.2 GB | 48.6 GB | Too big | Get file → | |
| Q2_K_L | 45.6 GB | 49.0 GB | Too big | Get file → | |
| IQ3_XXS | 47.0 GB | 50.5 GB | Too big | Get file → | |
| IQ3_XS | 50.1 GB (2 parts) | 53.6 GB | Too big | Get file → | |
| Q3_K_S | 52.8 GB (2 parts) | 56.3 GB | Too big | Get file → | |
| IQ3_M | 55.3 GB (2 parts) | 58.7 GB | Too big | Get file → | |
| Q3_K_M | 59.1 GB (2 parts) | 62.6 GB | Too big | Get file → | |
| Q3_K_L | 64.6 GB (2 parts) | 68.0 GB | Too big | Get file → | |
| Q3_K_XL | 64.9 GB (2 parts) | 68.4 GB | Too big | Get file → | |
| IQ4_XS | 65.4 GB (2 parts) | 68.9 GB | Too big | Get file → | |
| IQ4_NL | 69.2 GB (2 parts) | 72.7 GB | Too big | Get file → | |
| Q4_0 | 69.3 GB (2 parts) | 72.8 GB | Too big | Get file → | |
| Q4_K_S | 69.6 GB (2 parts) | 73.0 GB | Too big | Get file → | |
| Q4_K_M | 73.2 GB (2 parts) | 76.7 GB | Too big | Get file → | |
| Q4_K_L | 73.5 GB (2 parts) | 77.0 GB | Too big | Get file → | |
| Q4_1 | 76.7 GB (2 parts) | 80.2 GB | Too big | Get file → | |
| Q5_K_S | 84.4 GB (3 parts) | 87.8 GB | Too big | Get file → | |
| Q5_K_M | 86.5 GB (3 parts) | 89.9 GB | Too big | Get file → | |
| Q6_K | 100.6 GB (3 parts) | 104.0 GB | Too big | Get file → | |
| Q8_0 | 130.3 GB (4 parts) | 133.7 GB | Too big | Get file → |
For 8 GB VRAM, use the IQ1_S quant (25.96 GB file, 29.4 GB memory at 8 k context). For 16 GB VRAM, IQ2_XS (36.08 GB file, 39.5 GB memory) or Q2_K (45.2 GB file, 48.6 GB memory) are suitable. For 24 GB VRAM, Q3_K_M (59.1 GB file, 62.6 GB memory) or Q4_K_M (73.22 GB file, 76.7 GB memory) provide a balance between quality and memory usage.
What GPU do you need for Behemoth ReduX 123B v1.1?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 3.5 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 3.5 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 3.5 GB in use).
- 12 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 3.5 GB in use).
- 16 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 3.5 GB in use).
- 24 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 3.5 GB in use).
- 32 GB VRAM: the best quant that fits is IQ1_M (28.4 GB file, about 31.8 GB in use).
- 48 GB VRAM: the best quant that fits is IQ2_M (41.6 GB file, about 45.1 GB in use).
Which Behemoth ReduX 123B v1.1 quant should you choose?
Q4_K_M is the usual starting point for Behemoth ReduX 123B v1.1: it balances file size and quality well. Here it is a 73.2 GB file.
The Q8_0 file is 130.3 GB, about 1.8 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Behemoth ReduX 123B v1.1
How much VRAM does Behemoth ReduX 123B v1.1 need?
About 76.7 GB at Q4_K_M with an 8K context window. That is the 73.2 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run Behemoth ReduX 123B v1.1 on an 8 GB GPU?
Yes, with the smaller files: the 0.0 GB file needs about 3.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Behemoth ReduX 123B v1.1 GGUF?
It depends on the quant: file is 0.0 GB, IQ1_S is 26.0 GB, IQ1_M is 28.4 GB, IQ2_XXS is 32.4 GB, IQ2_XS is 36.1 GB, IQ2_S is 38.4 GB and 21 more.
What context length does Behemoth ReduX 123B v1.1 support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 3.0 GB at 8K and 11.8 GB at 32K.
Where can I download Behemoth ReduX 123B v1.1 GGUF?
The files are on Hugging Face in the bartowski/TheDrummer_Behemoth-ReduX-123B-v1.1-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run Q4_K_M on 12 GB VRAM?
No, Q4_K_M requires approximately 76.7 GB memory at 8 k context, which exceeds 12 GB VRAM.
Does the model support image inputs?
No, the model does not include vision capabilities.
Is the license free for commercial use?
The license is not specified, so verify usage rights before commercial deployment.