EBAI needs about 9.1 GB of memory at its main file (a 8.1 GB file) with an 8K context window, so it fits on a 12 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 1.9 GB.
EBAI is a 7.62B-parameter Ebai model in GGUF format, quantized by vathvathv. Its trained context length is 128K tokens. The repository has 1 quant file, from 8.1 GB to 8.1 GB.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 8.1 GB | 9.1 GB | Too big | Get file → |
What GPU do you need for EBAI?
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: the best quant that fits is the main file (8.1 GB file, about 9.1 GB in use).
Specifications
Architecture from the GGUF header
Frequently asked questions about EBAI
How much VRAM does EBAI need?
About 9.1 GB at its main file with an 8K context window. That is the 8.1 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 EBAI on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 9.1 GB, so you would need a larger GPU or CPU offloading.
What is the file size of EBAI GGUF?
It depends on the quant: file is 8.1 GB.
What context length does EBAI support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.5 GB at 8K and 1.9 GB at 32K.
Where can I download EBAI GGUF?
The files are on Hugging Face in the vathvathv/EBAI repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.