VOOZH about

URL: https://willitrunai.com/can-run/phi-4-mini-reasoning-on-arc-a380-6gb


Can Phi-4 Mini Reasoning 4B run on Intel Arc A380 6GB?

YES — Tight Fit

S88Excellent
Estimated from fit model

Phi-4 Mini Reasoning 4B needs ~5.3 GB VRAM. Intel Arc A380 6GB has 6.0 GB. With Q4_K_M quantization, expect ~39 tok/s.

Runtime: llama.cppCapacity: TightBandwidth: Very lowStack: StandardBottleneck: Memory bandwidth
Share:

Operating mode

Choose the run profile you care about

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.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 5.3 GB, 42.3 tok/s, Tight fit
5.3 GB required6.0 GB available
88% VRAM used

Fit status

Tight fit

Decode

42.3 tok/s

TTFT

4580 ms

Safe context

24K

Memory

5.3 GB / 6.0 GB

Memory breakdown

Weights2.3 GB
KV Cache1.5 GB
Runtime0.9 GB
Headroom0.6 GB

See how fast it feels

See how fast it feelsPhi-4 Mini Reasoning 4B on Intel Arc A380 6GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step. Given information: - Speed = 60 mph (miles per hour) - Time = 2.5 hours Formula: Distance = Speed x Time Calculation: Distance = 60 mph x 2.5 h = 150 miles The train travels 150 miles. Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time. Breakdown: - First half: 1.25 hours at 60 mph = 75 miles - Stop: 20 minutes (no distance) - Second half: 1.25 hours at 60 mph = 75 miles Total distance: 150 miles (same) Total time: 2.5 h + 0.33 h = 2.83 hours Average speed: 150 / 2.83 = 53 mph The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 42.3 tok/s decode · 4.6s TTFT (warm) · 106 tok/s prefill

What limits this setup

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.

Best improvement path

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.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatSRuns well42.3 tok/s2498 ms24K
CodingSTight fit39.3 tok/s4924 ms24K
Agentic CodingAVery compromised (needs ~0.3 GB host RAM)24.8 tok/s11374 ms24K
ReasoningSTight fit42.3 tok/s5413 ms24K
RAGAVery compromised (needs ~0.3 GB host RAM)24.8 tok/s14218 ms

Quantization options

How Phi-4 Mini Reasoning 4B (3.799999952316284B params) fits at each quantization level on Intel Arc A380 6GB (6.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
1.5 GB
LowS91
Q3_K_S
3
1.9 GB
LowS92
NVFP4
4

Get started

Copy-paste commands to run Phi-4 Mini Reasoning 4B on your machine.

Run

ollama run phi4-mini

Your hardware

More models your Intel Arc A380 6GB can run

ModelParamsGradeDecodeCapabilities
👁 Alibaba
Qwen 3.5 4B
4BS28.7 tok/s

Frequently asked questions

See all results for Intel Arc A380 6GBSee all hardware for Phi-4 Mini Reasoning 4B
24K
2.1 GB
Medium
S92
Q4_K_M
4
2.3 GB
MediumS91
Q5_K_M
5
2.7 GB
HighS91
Q6_KBest for your GPU
6
3.1 GB
HighS91
Q8_0
8
4.1 GB
Very HighF0
F16
16
7.8 GB
MaximumF0

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.