beam reap 255b needs about 4.8 GB of memory at BF16 (a 3.9 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 9 quants, from 0.3 GB to 139.6 GB (MXFP4).
beam reap 255b is a 255B-parameter Beam model in GGUF format, quantized by nbKPS. Its trained context length is 1024K tokens. The repository has 9 quant files, from 0.3 GB to 139.6 GB (MXFP4).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.3 GB | 0.9 GB | Fits | Get file → | |
| — | 0.3 GB | 0.9 GB | Fits | Get file → | |
| — | 0.7 GB | 1.2 GB | Fits | Get file → | |
| — | 1.3 GB | 2.0 GB | Fits | Get file → | |
| BF16 | 3.9 GB | 4.8 GB | Fits | Get file → | |
| — | 65.7 GB | 74.1 GB | Too big | Get file → | |
| — | 65.7 GB | 74.1 GB | Too big | Get file → | |
| — | 65.7 GB | 74.1 GB | Too big | Get file → | |
| MXFP4 | 139.6 GB (3 parts) | 156.9 GB | Too big | Get file → |
What GPU do you need for beam reap 255b?
These figures add the file size, an fp16 KV cache at an 8K context window 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 (1.3 GB file, about 2.0 GB in use).
- 6 GB VRAM: the best quant that fits is BF16 (3.9 GB file, about 4.8 GB in use).
- 8 GB VRAM: the best quant that fits is BF16 (3.9 GB file, about 4.8 GB in use).
- 12 GB VRAM: the best quant that fits is BF16 (3.9 GB file, about 4.8 GB in use).
- 16 GB VRAM: the best quant that fits is BF16 (3.9 GB file, about 4.8 GB in use).
- 24 GB VRAM: the best quant that fits is BF16 (3.9 GB file, about 4.8 GB in use).
- 32 GB VRAM: the best quant that fits is BF16 (3.9 GB file, about 4.8 GB in use).
- 48 GB VRAM: the best quant that fits is BF16 (3.9 GB file, about 4.8 GB in use).
Which beam reap 255b quant should you choose?
BF16 (3.9 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 the first one in the table at 0.3 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 beam reap 255b
How much VRAM does beam reap 255b need?
About 4.8 GB at BF16 with an 8K context window. That is the 3.9 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 beam reap 255b on an 8 GB GPU?
Yes, with BF16: the 3.9 GB file needs about 4.8 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of beam reap 255b GGUF?
It depends on the quant: file is 0.3 GB, file is 0.3 GB, file is 0.7 GB, file is 1.3 GB, BF16 is 3.9 GB, file is 65.7 GB and 3 more.
What context length does beam reap 255b support?
The GGUF header lists a trained context length of 1,048,576 tokens (1024K).
Where can I download beam reap 255b GGUF?
The files are on Hugging Face in the nbKPS/beam-reap-255b-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 beam reap 255b 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.