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.
~$10,000 MSRP
![]() |
VOOZH | about |
Qwen 3.6 35B A3B needs ~27.9 GB VRAM. Intel Arc Pro B60 24GB has 24.0 GB. With NVFP4 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
5.7 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
15.5 tok/s
TTFT
12454 ms
Safe context
4K
Memory
29.7 GB / 24.0 GB
Offload
20%
It fits through host-memory offload, and offload is the main reason performance drops.
CPU or host-memory offload is active
About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.
Very little memory headroom
You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.
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.
Remove offload with more accelerator memory
Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
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.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | A | Very compromised (needs ~2.8 GB host RAM) | 18.0 tok/s | 5869 ms | 4K |
| Coding | F | Too heavy | 15.5 tok/s | 12454 ms | 4K |
| Agentic Coding | F | Too heavy | 11.9 tok/s | 23595 ms | 4K |
| Reasoning | F | Too heavy | 15.5 tok/s | 14719 ms | 4K |
| RAG | F | Too heavy | 11.9 tok/s | 29494 ms | 4K |
How Qwen 3.6 35B A3B (35B params) fits at each quantization level on Intel Arc Pro B60 24GB (24.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 13.7 GB | Low | S92 |
Q3_K_SBest for your GPU | 3 | 17.2 GB | Low | S92 |
NVFP4 | 4 | 19.6 GB | Medium | F0 |
Q4_K_M | 4 | 21.3 GB | Medium | F0 |
Q5_K_M | 5 | 25.2 GB | High | F0 |
Q6_K | 6 | 28.7 GB | High | F0 |
Q8_0 | 8 | 37.5 GB | Very High | F0 |
F16 | 16 | 71.8 GB | Maximum | F0 |
Copy-paste commands to run Qwen 3.6 35B A3B on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "Qwen/Qwen3.6-35B-A3B" \
--hf-file "Qwen3.6-35B-A3B-Q4_K_M.gguf" \
-c 4096 -ngl 99Upgrade options
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.
~$10,000 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.
~$15,000 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.
~$15,000 MSRP