FINAL Bench.Darwin 36B Opus needs about 22.3 GB of memory at F16 (a 21.2 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 6 quants, from 12.9 GB (F16) to 36.9 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 2.7 GB.
FINAL Bench.Darwin 36B Opus is a 34.7B-parameter Darwin model in GGUF format, quantized by DevQuasar. Its trained context length is 256K tokens. The repository has 6 quant files, from 12.9 GB (F16) to 36.9 GB (F16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| F16 | 12.9 GB | 14.1 GB | Too big | Get file → | |
| F16 | 16.8 GB | 17.9 GB | Too big | Get file → | |
| F16 | 21.2 GB | 22.3 GB | Too big | Get file → | |
| F16 | 24.7 GB | 25.9 GB | Too big | Get file → | |
| F16 | 28.5 GB | 29.7 GB | Too big | Get file → | |
| F16 | 36.9 GB | 38.1 GB | Too big | Get file → |
What GPU do you need for FINAL Bench.Darwin 36B Opus?
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: the best quant that fits is F16 (12.9 GB file, about 14.1 GB in use).
- 24 GB VRAM: the best quant that fits is F16 (21.2 GB file, about 22.3 GB in use).
- 32 GB VRAM: the best quant that fits is F16 (28.5 GB file, about 29.7 GB in use).
- 48 GB VRAM: the best quant that fits is F16 (36.9 GB file, about 38.1 GB in use).
Which FINAL Bench.Darwin 36B Opus quant should you choose?
F16 (21.2 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 12.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 FINAL Bench.Darwin 36B Opus
How much VRAM does FINAL Bench.Darwin 36B Opus need?
About 22.3 GB at F16 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 FINAL Bench.Darwin 36B Opus on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 14.1 GB, so you would need a larger GPU or CPU offloading.
What is the file size of FINAL Bench.Darwin 36B Opus GGUF?
It depends on the quant: F16 is 12.9 GB, F16 is 16.8 GB, F16 is 21.2 GB, F16 is 24.7 GB, F16 is 28.5 GB, F16 is 36.9 GB.
What context length does FINAL Bench.Darwin 36B Opus 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 FINAL Bench.Darwin 36B Opus GGUF?
The files are on Hugging Face in the DevQuasar/FINAL-Bench.Darwin-36B-Opus-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 FINAL Bench.Darwin 36B Opus 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.