telco troubleshooting agentic challenge needs about 22.3 GB of memory at Q4_K_M (a 21.2 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 6 quants, from 6.5 GB (IQ4_XS) to 69.4 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 2.7 GB.
telco troubleshooting agentic challenge is a 34.7B-parameter Merged model in GGUF format, quantized by andreribeiro87. Its trained context length is 256K tokens. The repository has 6 quant files, from 6.5 GB (IQ4_XS) to 69.4 GB (BF16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ4_XS | 6.5 GB | 7.7 GB | Tight | Get file → | |
| BF16 | 19.5 GB | 20.7 GB | Too big | Get file → | |
| BF16 | 19.5 GB | 20.7 GB | Too big | Get file → | |
| IQ4_NL | 19.8 GB | 21.0 GB | Too big | Get file → | |
| Q4_K_M | 21.2 GB | 22.3 GB | Too big | Get file → | |
| BF16 | 69.4 GB (2 parts) | 70.5 GB | Too big | Get file → |
What GPU do you need for telco troubleshooting agentic challenge?
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: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: the best quant that fits is IQ4_XS (6.5 GB file, about 7.7 GB in use).
- 12 GB VRAM: the best quant that fits is IQ4_XS (6.5 GB file, about 7.7 GB in use).
- 16 GB VRAM: the best quant that fits is IQ4_XS (6.5 GB file, about 7.7 GB in use).
- 24 GB VRAM: the best quant that fits is Q4_K_M (21.2 GB file, about 22.3 GB in use).
- 32 GB VRAM: the best quant that fits is Q4_K_M (21.2 GB file, about 22.3 GB in use).
- 48 GB VRAM: the best quant that fits is Q4_K_M (21.2 GB file, about 22.3 GB in use).
Which telco troubleshooting agentic challenge quant should you choose?
Q4_K_M is the usual starting point for telco troubleshooting agentic challenge: it balances file size and quality well. Here it is a 21.2 GB file.
If memory is tight, the smallest file is IQ4_XS at 6.5 GB, with the quality trade-offs that come with fewer bits. The usual sweet spot between file size and quality, and the quant most people start with.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about telco troubleshooting agentic challenge
How much VRAM does telco troubleshooting agentic challenge need?
About 22.3 GB at Q4_K_M with an 8K context window. That is the 21.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 telco troubleshooting agentic challenge on an 8 GB GPU?
Yes, with IQ4_XS: the 6.5 GB file needs about 7.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of telco troubleshooting agentic challenge GGUF?
It depends on the quant: IQ4_XS is 6.5 GB, BF16 is 19.5 GB, BF16 is 19.5 GB, IQ4_NL is 19.8 GB, Q4_K_M is 21.2 GB, BF16 is 69.4 GB.
What context length does telco troubleshooting agentic challenge support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.7 GB at 8K and 2.7 GB at 32K.
Where can I download telco troubleshooting agentic challenge GGUF?
The files are on Hugging Face in the andreribeiro87/telco-troubleshooting-agentic-challenge-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does telco troubleshooting agentic challenge use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.