Hcompany.Holotron4 30B A3B needs about 32.0 GB of memory at F16 (a 24.5 GB file) with an 8K context window, so it fits on a 32 GB GPU. This repository has 6 quants, from 17.9 GB (F16) to 33.6 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 27.9 GB.
Hcompany.Holotron4 30B A3B is a 31.6B-parameter Holotron model in GGUF format, quantized by DevQuasar. Its trained context length is 1024K tokens. The repository has 6 quant files, from 17.9 GB (F16) to 33.6 GB (F16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| F16 | 17.9 GB | 25.4 GB | Too big | Get file → | |
| F16 | 19.8 GB | 27.3 GB | Too big | Get file → | |
| F16 | 24.5 GB | 32.0 GB | Too big | Get file → | |
| F16 | 26.0 GB | 33.5 GB | Too big | Get file → | |
| F16 | 33.5 GB | 41.0 GB | Too big | Get file → | |
| F16 | 33.6 GB | 41.1 GB | Too big | Get file → |
What GPU do you need for Hcompany.Holotron4 30B A3B?
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: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: no quant fits at an 8K context.
- 32 GB VRAM: the best quant that fits is F16 (24.5 GB file, about 32.0 GB in use).
- 48 GB VRAM: the best quant that fits is F16 (33.6 GB file, about 41.1 GB in use).
Which Hcompany.Holotron4 30B A3B quant should you choose?
F16 (24.5 GB) is the middle option in this repository. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
If memory is tight, the smallest file is F16 at 17.9 GB, with the quality trade-offs that come with fewer bits. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Hcompany.Holotron4 30B A3B
How much VRAM does Hcompany.Holotron4 30B A3B need?
About 32.0 GB at F16 with an 8K context window. That is the 24.5 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 Hcompany.Holotron4 30B A3B on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 25.4 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Hcompany.Holotron4 30B A3B GGUF?
It depends on the quant: F16 is 17.9 GB, F16 is 19.8 GB, F16 is 24.5 GB, F16 is 26.0 GB, F16 is 33.5 GB, F16 is 33.6 GB.
What context length does Hcompany.Holotron4 30B A3B support?
The GGUF header lists a trained context length of 1,048,576 tokens (1024K). The KV cache grows with the context you use: about 7.0 GB at 8K and 27.9 GB at 32K.
Where can I download Hcompany.Holotron4 30B A3B GGUF?
The files are on Hugging Face in the DevQuasar/Hcompany.Holotron4-30B-A3B-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 Hcompany.Holotron4 30B A3B use?
Hugging Face lists the license as other. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.