Makes the model fit on the accelerator instead of staying completely out of reach.
Raises estimated decode speed by about 189%.
〜$349 MSRP
Codestral 22B v0.1 needs ~17.9 GB but Intel Arc B570 10GB only has 10.0 GB. Try a smaller quantization or lighter model.
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
7.9 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
3.6 tok/s
TTFT
54289 ms
Safe context
4K
Memory
17.9 GB / 10.0 GB
Offload
40%
Usable VRAM is the main blocker for this model.
Not enough usable memory
The model needs 17.9 GB, but this setup only exposes 10.0 GB of usable VRAM.
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.
Add more VRAM headroom
The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.
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 | F | Too heavy | 4.2 tok/s | 25424 ms | 4K |
| Coding | F | Too heavy | 3.6 tok/s | 54289 ms | 4K |
| Agentic Coding | F | Too heavy | 2.7 tok/s | 103912 ms | 4K |
| Reasoning | F | Too heavy | 3.6 tok/s | 64160 ms | 4K |
| RAG | F | Too heavy | 2.7 tok/s | 129890 ms | 4K |
How Codestral 22B v0.1 (22B params) fits at each quantization level on Intel Arc B570 10GB (10.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 8.6 GB | Low | F0 |
Q3_K_S | 3 | 10.8 GB | Low | F0 |
NVFP4 | 4 | 12.3 GB | Medium | F0 |
Q4_K_M | 4 | 13.4 GB | Medium | F0 |
Q5_K_M | 5 | 15.8 GB | High | F0 |
Q6_K | 6 | 18.0 GB | High | F0 |
Q8_0 | 8 | 23.5 GB | Very High | F0 |
F16 | 16 | 45.1 GB | Maximum | F0 |
アップグレードオプション
Makes the model fit on the accelerator instead of staying completely out of reach.
Raises estimated decode speed by about 189%.
〜$349 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Raises estimated decode speed by about 42%.
〜$399 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
〜$599 MSRP
No, Codestral 22B v0.1 requires more memory than Intel Arc B570 10GB provides.
Codestral 22B v0.1 (22B parameters) requires approximately 17.9 GB of memory with Q4_K_M quantization.
The recommended quantization for Codestral 22B v0.1 is Q4_K_M, which balances quality and memory efficiency.
On Intel Arc B570 10GB, Codestral 22B v0.1 achieves approximately 3.6 tokens per second decode speed with a time-to-first-token of 54289ms using Q4_K_M quantization.
For coding workloads, Codestral 22B v0.1 on Intel Arc B570 10GB receives a F grade with 3.6 tok/s and 4K context.
On Intel Arc B570 10GB, Codestral 22B v0.1 can safely use up to 4K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.
Add more VRAM headroom. The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.
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.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/hf-lmstudio-community--codestral-22b-v0-1-gguf-on-arc-b570-10gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: