Raises estimated decode speed by about 186%.
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
EXAONE 3.5 7.8B Instruct needs ~9.0 GB VRAM. Intel Arc Pro B60 24GB has 24.0 GB. With Q4_K_M quantization, expect ~52 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
51.8 tok/s
TTFT
3741 ms
Safe context
279K
Memory
9.0 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 | 51.8 tok/s | 2040 ms | 279K |
| Coding | C | Runs well | 51.8 tok/s | 3741 ms | 279K |
| Agentic Coding | C | Runs well | 51.8 tok/s | 5441 ms | 279K |
| Reasoning | C | Runs well | 51.8 tok/s | 4421 ms | 279K |
| RAG | C | Runs well | 51.8 tok/s | 6802 ms | 279K |
How EXAONE 3.5 7.8B Instruct (7.800000190734863B params) fits at each quantization level on Intel Arc Pro B60 24GB (24.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 3.0 GB | Low | C44 |
Q3_K_S | 3 | 3.8 GB | Low | C45 |
NVFP4 | 4 | 4.4 GB | Medium | C45 |
Q4_K_M | 4 | 4.8 GB | Medium | C45 |
Q5_K_M | 5 | 5.6 GB | High | C46 |
Q6_K | 6 | 6.4 GB | High | C46 |
Q8_0 | 8 | 8.3 GB | Very High | C47 |
F16Best for your GPU | 16 | 16.0 GB | Maximum | C50 |
Copy-paste commands to run EXAONE 3.5 7.8B Instruct on your machine.
Run
lms load hf-lmstudio-community--exaone-3-5-7-8b-instruct-gguf && lms server startアップグレードオプション
Raises estimated decode speed by about 186%.
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
〜$2,499 MSRP
Yes, Intel Arc Pro B60 24GB can run EXAONE 3.5 7.8B Instruct with a C grade (Runs well). Expected decode speed: 51.8 tok/s.
EXAONE 3.5 7.8B Instruct (7.800000190734863B parameters) requires approximately 9.0 GB of memory with Q4_K_M quantization.
The recommended quantization for EXAONE 3.5 7.8B Instruct is Q4_K_M, which balances quality and memory efficiency.
On Intel Arc Pro B60 24GB, EXAONE 3.5 7.8B Instruct achieves approximately 51.8 tokens per second decode speed with a time-to-first-token of 3741ms using Q4_K_M quantization.
For coding workloads, EXAONE 3.5 7.8B Instruct on Intel Arc Pro B60 24GB receives a C grade with 51.8 tok/s and 279K context.
On Intel Arc Pro B60 24GB, EXAONE 3.5 7.8B Instruct can safely use up to 279K 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-lmstudio-community--exaone-3-5-7-8b-instruct-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: