Jamba 1.5 Mini
12BAI21 Labs
⚠ Superseded · Prefer Ministral 3 8B Instruct
This index would suggest Ministral 3 8B Instruct instead today — more quant levels to choose from (2 → 3). The numbers below are still accurate; they are just for a model you probably should not start with. Compare the two →
Hybrid SSM-Transformer with 256K context. Efficient long-document QA on 16GB.
262K
Max Context
2
Quant Variants
GGUF Q4_K_M
Best Quality
96.6%
Accuracy Retained
Quantization Variants
Per-quant VRAM, quality loss, and inference speed on RTX 4090
Measured = site benchmarks · Estimated = formula · Community = public reports
Similar models
Compare with Qwen2.5 14BQwen2.5 14B Instruct
Alibaba Qwen2.5
The sweet spot between performance and resource usage. 16GB VRAM with Q4.
Mistral Nemo 12B Instruct
Mistral AI
Mistral + NVIDIA collaboration. 128K context, excellent multilingual support.
Gemma 2 9B Instruct
Google Gemma 2
Google's compact Gemma 2 with sliding window attention. Punches above 9B.
Solar 10.7B Instruct
Upstage
Depth-upscaled 10.7B punching above weight. Strong on reasoning benchmarks.
Running Jamba 1.5 Mini locally
At Q4_K_M and 4K of context, Jamba 1.5 Mini needs about 8.2 GB — 6.9 GB of weights, 0.50 GB of KV cache and a 0.7 GB activation buffer. The smallest card in this index that clears that comfortably is the RTX 3080 10G at 10 GB, and 56 of the 63 cards here do. These are calculated figures, not measurements: the estimate stops counting a card as comfortable at 88% of its VRAM, which is roughly the room a desktop session needs.
What longer context costs
Going from 4K to 32K adds about 3.50 GB, taking the total to 12.0 GB. Weights do not move with context — only the KV cache does, and it grows linearly, so this is the number to watch when planning for long documents. The model's native window is 256K; holding all of it at Q4_K_M would need about 43 GB.
Which build to download
This index tracks 2 formats for it — GGUF, AWQ — across 2 levels. Q4_K_M carries the lowest published perplexity loss at 3.4%. The fastest level measured here is AWQ INT4 at 125 tok/s on an RTX 4090, batch 1. GGUF runs on llama.cpp and Ollama across NVIDIA, AMD and Apple silicon; AWQ and GPTQ target vLLM on CUDA and ROCm; EXL2 is ExLlamaV2 and CUDA only.
Common questions
- How much VRAM does Jamba 1.5 Mini need?
- About 8.2 GB at Q4_K_M with 4K of context and batch 1, rising to roughly 12.0 GB at 32K. That figure is weights plus KV cache plus a 10% activation buffer, calculated from the model's architecture rather than measured on a card.
- Will Jamba 1.5 Mini run on a 10GB GPU?
- Yes — at Q4_K_M and 4K context it needs about 8.2 GB, which leaves 1.8 GB spare on a RTX 3080 10G. That is the smallest card in this index that clears it comfortably; 56 of 63 do.
- Which quantization of Jamba 1.5 Mini should I use?
- Q4_K_M has the lowest published quality loss (3.4%), and Q4_K_M is the level most people run. All 2 levels in the index are Q4_K_M, AWQ INT4.
Where this model fits
Sized at Q4_K_M with a 4K context window, smallest card first. Comfortable means the estimate uses at most 88% of the memory.
- Runs comfortably on
- RTX 3080 10G10GB · +1.8RTX 507012GB · +3.9RTX 4070 Ti12GB · +3.9RTX 4070 Super12GB · +3.9RTX 407012GB · +3.9
- Tight but possible
- RTX 5060 Ti 8G8GBRTX 50608GBRTX 4060 Ti 8G8GB
- Just misses
- Mac M3 8G+2.2GB over
- Compared here
- GGUF vs AWQ
- Try it yourself
- Size it in the calculatorGenerate the run command
How to actually run this
Deployment guides for this model and this class of hardware.
This page's figures change when the model or the runtime does.Last updated 2026-09-21 RSS → /feed.xml