ai21labs AI21 Jamba2 3B needs ~3.7 GB VRAM. Intel Arc A380 6GB has 6.0 GB. With Q4_K_M quantization, expect ~42 tok/s.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
Fit status
Runs well
Decode
42.0 tok/s
TTFT
4610 ms
Safe context
122K
Memory
3.7 GB / 6.0 GB
The raw memory story may look fine, but the software ecosystem is still a constraint here.
Runtime ecosystem is narrower than CUDA
Intel GPUs can look attractive on memory per dollar, but local AI tooling, kernels, and model coverage are still broader and easier on CUDA today.
Prefer CUDA if you want the path of least resistance
If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | C | Runs well | 42.0 tok/s | 2514 ms | 122K |
| Coding | C | Runs well | 42.0 tok/s | 4610 ms | 122K |
| Agentic Coding | C | Runs well | 42.0 tok/s | 6705 ms | 122K |
| Reasoning | C | Runs well | 42.0 tok/s | 5448 ms | 122K |
| RAG | C | Runs well | 42.0 tok/s | 8381 ms | 122K |
How ai21labs AI21 Jamba2 3B (3B params) fits at each quantization level on Intel Arc A380 6GB (6.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 1.2 GB | Low | C53 |
Q3_K_S | 3 | 1.5 GB | Low | C53 |
NVFP4 | 4 |
Copy-paste commands to run ai21labs AI21 Jamba2 3B on your machine.
Run
lms load hf-bartowski--ai21labs-ai21-jamba2-3b-gguf && lms server startYes, Intel Arc A380 6GB can run ai21labs AI21 Jamba2 3B with a C grade (Runs well). Expected decode speed: 42.0 tok/s.
ai21labs AI21 Jamba2 3B (3B parameters) requires approximately 3.7 GB of memory with Q4_K_M quantization.
The recommended quantization for ai21labs AI21 Jamba2 3B is Q4_K_M, which balances quality and memory efficiency.
On Intel Arc A380 6GB, ai21labs AI21 Jamba2 3B achieves approximately 42.0 tokens per second decode speed with a time-to-first-token of 4610ms using Q4_K_M quantization.
For coding workloads, ai21labs AI21 Jamba2 3B on Intel Arc A380 6GB receives a C grade with 42.0 tok/s and 122K context.
On Intel Arc A380 6GB, ai21labs AI21 Jamba2 3B can safely use up to 122K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/hf-bartowski--ai21labs-ai21-jamba2-3b-gguf-on-arc-a380-6gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
| Medium |
| C54 |
Q4_K_M | 4 | 1.8 GB | Medium | C54 |
Q5_K_M | 5 | 2.2 GB | High | C54 |
Q6_K | 6 | 2.5 GB | High | C54 |
Q8_0Best for your GPU | 8 | 3.2 GB | Very High | C53 |
F16 | 16 | 6.1 GB | Maximum | F0 |
Prefer CUDA if you want the path of least resistance. If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.
Often yes, if your goal is the easiest setup and the widest runtime support. Intel can offer attractive memory capacity, but CUDA still tends to win on tooling maturity, guides, kernels, and model coverage for local AI.