ViAble 1.7 9B — Hardware Requirements & GPU Compatibility
ChatReasoning
ViAble 1.7 9B is a 9.0B-parameter open language model from bogairff55. It supports a context window of up to 262,144 tokens. At BF16 it needs about 18.48 GB of VRAM — see which GPUs and Macs can run it below.
1.1K downloads
3 likesSpecifications
- Publisher
- bogairff55
- Parameters
- 9.0B
- Architecture
- Qwen3_5ForCausalLM
- Context Length
- 262,144 tokens
- Vocabulary Size
- 248,320
- Release Date
- 2026-09-03
Get Started
HuggingFace
How Much VRAM Does ViAble 1.7 9B Need?
Select a quantization to see compatible GPUs below.
| Quantization | Bits | VRAM | + Context | File Size | Quality |
|---|---|---|---|---|---|
| BF16est. | 16.00 | 18.5 GB | 52.6 GB | 17.91 GB | Brain floating point 16 — preferred for training |
est.= calculated VRAM estimate; no published GGUF file found for that quantization yet. Other rows are verified against real community uploads.
Which GPUs Can Run ViAble 1.7 9B?
BF16 · 18.5 GBViAble 1.7 9B (BF16) requires 18.5 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 25+ GB is recommended. Using the full 262K context window can add up to 34.1 GB, bringing total usage to 52.6 GB. 8 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti.
Runs great
— Plenty of headroom
Which Devices Can Run ViAble 1.7 9B?
BF16 · 18.5 GB41 devices with unified memory can run ViAble 1.7 9B, including NVIDIA DGX H100, NVIDIA DGX A100 640GB, Mac Mini M4 Pro (24 GB).
Runs great
— Plenty of headroomDecent
— Enough memory, may be tightRelated Models
Frequently Asked Questions
- How much VRAM does ViAble 1.7 9B need?
ViAble 1.7 9B requires 18.5 GB of VRAM at BF16. Full 262K context adds up to 34.1 GB (52.6 GB total).
VRAM = Weights + KV Cache + Overhead
Weights = 9.0B × 16 bits ÷ 8 = 17.9 GB
KV Cache + Overhead ≈ 0.6 GB (at 2K context + ~0.3 GB framework)
KV Cache + Overhead ≈ 34.7 GB (at full 262K context)
VRAM usage by quantization
BF1618.5 GBBF16 + full context52.6 GB- Can I run ViAble 1.7 9B on a Mac?
ViAble 1.7 9B requires at least 18.5 GB at BF16, which exceeds the unified memory of most consumer Macs. You would need a Mac Studio or Mac Pro with a high-memory configuration.
- Can I run ViAble 1.7 9B locally?
Yes — ViAble 1.7 9B can run locally on consumer hardware. At BF16 quantization it needs 18.5 GB of VRAM. Popular tools include Ollama, LM Studio, and llama.cpp.
- How fast is ViAble 1.7 9B?
At BF16, ViAble 1.7 9B can reach ~260 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~36 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.
tok/s = (bandwidth GB/s ÷ model GB) × efficiency
Example: NVIDIA B200 → 8000 ÷ 18.5 × 0.65 = ~281 tok/s
Estimated speed at BF16 (18.5 GB)
~281 tok/s~36 tok/s~281 tok/s~260 tok/sReal-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.
- What's the download size of ViAble 1.7 9B?
At BF16, the download is about 17.91 GB.
- Which GPUs can run ViAble 1.7 9B?
8 consumer GPUs can run ViAble 1.7 9B at BF16 (18.5 GB). Top options include NVIDIA GeForce RTX 5090, AMD Radeon RX 7900 XT, AMD Radeon RX 7900 XTX. 1 GPU have plenty of headroom for comfortable inference.
- Which devices can run ViAble 1.7 9B?
41 devices with unified memory can run ViAble 1.7 9B at BF16 (18.5 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Asus ROG Flow Z13 (2025, Ryzen AI Max+ 395, 128 GB), Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.