Claim Extractor 2B Q 2605 — Hardware Requirements & GPU Compatibility
Chat
Claim Extractor 2B Q 2605 is a 2.3B-parameter open language model from principled-intelligence. It supports a context window of up to 262,144 tokens. At BF16 it needs about 4.95 GB of VRAM — see which GPUs and Macs can run it below.
339 downloads
5 likesSpecifications
- Publisher
- principled-intelligence
- Parameters
- 2.3B
- Architecture
- Qwen3_5ForConditionalGeneration
- Context Length
- 262,144 tokens
- Vocabulary Size
- 248,320
- Release Date
- 2026-05-14
- License
- Apache 2.0
Get Started
How Much VRAM Does Claim Extractor 2B Q 2605 Need?
Select a quantization to see compatible GPUs below.
| Quantization | Bits | VRAM | + Context | File Size | Quality |
|---|---|---|---|---|---|
| BF16 | 16.00 | 5.0 GB | 17.7 GB | 4.55 GB | Brain floating point 16 — preferred for training |
Which GPUs Can Run Claim Extractor 2B Q 2605?
BF16 · 5.0 GBClaim Extractor 2B Q 2605 (BF16) requires 5.0 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 7+ GB is recommended. Using the full 262K context window can add up to 12.8 GB, bringing total usage to 17.7 GB. 35 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti.
Runs great
— Plenty of headroomWhich Devices Can Run Claim Extractor 2B Q 2605?
BF16 · 5.0 GB33 devices with unified memory can run Claim Extractor 2B Q 2605, including NVIDIA DGX H100, NVIDIA DGX A100 640GB.
Runs great
— Plenty of headroomRelated Models
Frequently Asked Questions
- How much VRAM does Claim Extractor 2B Q 2605 need?
Claim Extractor 2B Q 2605 requires 5.0 GB of VRAM at BF16. Full 262K context adds up to 12.8 GB (17.7 GB total).
VRAM = Weights + KV Cache + Overhead
Weights = 2.3B × 16 bits ÷ 8 = 4.5 GB
KV Cache + Overhead ≈ 0.5 GB (at 2K context + ~0.3 GB framework)
KV Cache + Overhead ≈ 13.2 GB (at full 262K context)
VRAM usage by quantization
BF165.0 GBBF16 + full context17.7 GB- Can I run Claim Extractor 2B Q 2605 on a Mac?
Claim Extractor 2B Q 2605 requires at least 5.0 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 Claim Extractor 2B Q 2605 locally?
Yes — Claim Extractor 2B Q 2605 can run locally on consumer hardware. At BF16 quantization it needs 5.0 GB of VRAM. Popular tools include Ollama, LM Studio, and llama.cpp.
- How fast is Claim Extractor 2B Q 2605?
At BF16, Claim Extractor 2B Q 2605 can reach ~589 tok/s on AMD Instinct MI300X. On NVIDIA GeForce RTX 4090: ~132 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.
tok/s = (bandwidth GB/s ÷ model GB) × efficiency
Example: AMD Instinct MI300X → 5300 ÷ 5.0 × 0.55 = ~589 tok/s
Estimated speed at BF16 (5.0 GB)
~589 tok/s~132 tok/s~440 tok/s~364 tok/sReal-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.
- What's the download size of Claim Extractor 2B Q 2605?
At BF16, the download is about 4.55 GB.
- Which GPUs can run Claim Extractor 2B Q 2605?
35 consumer GPUs can run Claim Extractor 2B Q 2605 at BF16 (5.0 GB). Top options include AMD Radeon RX 6700 XT, AMD Radeon RX 6800, AMD Radeon RX 6800 XT. 35 GPUs have plenty of headroom for comfortable inference.
- Which devices can run Claim Extractor 2B Q 2605?
33 devices with unified memory can run Claim Extractor 2B Q 2605 at BF16 (5.0 GB), including Mac Mini M4 (16 GB), Mac Mini M4 (32 GB), Mac Mini M4 Pro (24 GB), Mac Mini M4 Pro (48 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.