Raises estimated decode speed by about 344%.
Adds memory headroom for longer context windows and future model growth.
This is not only a hardware jump. It also gives you a cleaner runtime ecosystem for local LLM tooling.
~$1,999 MSRP
internlm2 5 20b chat needs ~17.8 GB VRAM. Intel Arc Pro B60 24GB has 24.0 GB. With Q4_K_M quantization, expect ~20 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
20.2 tok/s
TTFT
9592 ms
Safe context
58K
Memory
17.8 GB / 24.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 | 20.2 tok/s | 5232 ms | 58K |
| Coding | C | Runs well | 20.2 tok/s | 9592 ms | 58K |
| Agentic Coding | C | Tight fit | 20.2 tok/s | 13952 ms | 58K |
| Reasoning | C | Runs well | 20.2 tok/s | 11336 ms | 58K |
| RAG | C | Tight fit | 20.2 tok/s | 17440 ms | 58K |
How internlm2 5 20b chat (20B params) fits at each quantization level on Intel Arc Pro B60 24GB (24.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 7.8 GB | Low | C47 |
Q3_K_S | 3 | 9.8 GB | Low | C48 |
NVFP4 | 4 | 11.2 GB | Medium | C49 |
Q4_K_M | 4 | 12.2 GB | Medium | C50 |
Q5_K_M | 5 | 14.4 GB | High | C50 |
Q6_KBest for your GPU | 6 | 16.4 GB | High | C49 |
Q8_0 | 8 | 21.4 GB | Very High | F0 |
F16 | 16 | 41.0 GB | Maximum | F0 |
Copy-paste commands to run internlm2 5 20b chat on your machine.
Run
lms load hf-bartowski--internlm2-5-20b-chat-gguf && lms server startOpções de upgrade
Raises estimated decode speed by about 344%.
Adds memory headroom for longer context windows and future model growth.
This is not only a hardware jump. It also gives you a cleaner runtime ecosystem for local LLM tooling.
~$1,999 MSRP
Raises estimated decode speed by about 40%.
~$2,499 MSRP
Yes, Intel Arc Pro B60 24GB can run internlm2 5 20b chat with a C grade (Runs well). Expected decode speed: 20.2 tok/s.
internlm2 5 20b chat (20B parameters) requires approximately 17.8 GB of memory with Q4_K_M quantization.
The recommended quantization for internlm2 5 20b chat is Q4_K_M, which balances quality and memory efficiency.
On Intel Arc Pro B60 24GB, internlm2 5 20b chat achieves approximately 20.2 tokens per second decode speed with a time-to-first-token of 9592ms using Q4_K_M quantization.
For coding workloads, internlm2 5 20b chat on Intel Arc Pro B60 24GB receives a C grade with 20.2 tok/s and 58K context.
On Intel Arc Pro B60 24GB, internlm2 5 20b chat can safely use up to 58K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.
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.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/hf-bartowski--internlm2-5-20b-chat-gguf-on-arc-pro-b60-24gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: