Removes host-memory offload, which is usually the single biggest latency and throughput win.
Raises estimated decode speed by about 141%.
~$349 MSRP
Phi 4 reasoning vision 15B needs ~13.0 GB VRAM. Intel Arc A730M 12GB has 12.0 GB. With Q4_K_M quantization, expect ~11 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
1.0 GB over capacity — needs offload or smaller quantization
Fit status
Very compromised (needs ~0.7 GB host RAM)
Decode
11.4 tok/s
TTFT
17000 ms
Safe context
7K
Memory
13.0 GB / 12.0 GB
Offload
10%
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 | C | Runs with offload (needs ~0.1 GB host RAM) | 13.2 tok/s | 8003 ms | 7K |
| Coding | D | Very compromised (needs ~0.7 GB host RAM) | 11.4 tok/s | 17000 ms | 7K |
| Agentic Coding | F | Too heavy | 8.7 tok/s | 32289 ms | 7K |
| Reasoning | D | Very compromised (needs ~0.7 GB host RAM) | 11.4 tok/s | 20091 ms | 7K |
| RAG | F | Too heavy | 8.7 tok/s | 40361 ms |
How Phi 4 reasoning vision 15B (15B params) fits at each quantization level on Intel Arc A730M 12GB (12.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 5.9 GB | Low | C52 |
Q3_K_S | 3 | 7.4 GB | Low | C52 |
NVFP4Best for your GPU |
Copy-paste commands to run Phi 4 reasoning vision 15B on your machine.
Run
lms load hf-jamesburton--phi-4-reasoning-vision-15b-gguf && lms server startUpgrade options
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Raises estimated decode speed by about 141%.
~$349 MSRP
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Adds memory headroom for longer context windows and future model growth.
~$399 MSRP
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Raises estimated decode speed by about 136%.
~$599 MSRP
Yes, Intel Arc A730M 12GB can run Phi 4 reasoning vision 15B with a D grade (Very compromised (needs ~0.7 GB host RAM)). Expected decode speed: 11.4 tok/s.
Phi 4 reasoning vision 15B (15B parameters) requires approximately 13.0 GB of memory with Q4_K_M quantization.
The recommended quantization for Phi 4 reasoning vision 15B is Q4_K_M, which balances quality and memory efficiency.
On Intel Arc A730M 12GB, Phi 4 reasoning vision 15B achieves approximately 11.4 tokens per second decode speed with a time-to-first-token of 17000ms using Q4_K_M quantization.
For coding workloads, Phi 4 reasoning vision 15B on Intel Arc A730M 12GB receives a D grade with 11.4 tok/s and 7K context.
On Intel Arc A730M 12GB, Phi 4 reasoning vision 15B can safely use up to 7K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/hf-jamesburton--phi-4-reasoning-vision-15b-gguf-on-arc-a730m-12gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
| 7K |
| 4 |
8.4 GB |
| Medium |
| C51 |
Q4_K_M | 4 | 9.2 GB | Medium | F0 |
Q5_K_M | 5 | 10.8 GB | High | F0 |
Q6_K | 6 | 12.3 GB | High | F0 |
Q8_0 | 8 | 16.1 GB | Very High | F0 |
F16 | 16 | 30.7 GB | Maximum | F0 |
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.
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.