Can LFM2.5 350M run on Intel Arc A380 6GB?
YES — Runs Great
LFM2.5 350M needs ~1.9 GB VRAM. Intel Arc A380 6GB has 6.0 GB. With Q4_K_M quantization, expect ~5 tok/s.
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.
Select quantization to explore
Fit status
Runs well
Decode
4.9 tok/s
TTFT
39510 ms
Safe context
128K
Memory
1.9 GB / 6.0 GB
Memory breakdown
See how fast it feels
What limits this setup
This model fits, but memory bandwidth is the part holding decode speed back.
Throughput will feel slow
Estimated decode speed is only 4.9 tok/s, so this is more of a technical fit than a comfortable daily-driver setup.
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
Prioritize bandwidth, not only capacity
If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
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
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | C | Runs well | 4.9 tok/s | 21551 ms | 128K |
| Coding | C | Runs well | 4.9 tok/s | 39510 ms | 128K |
| Agentic Coding | C | Runs well | 4.9 tok/s | 57469 ms | 128K |
| Reasoning | C | Runs well | 4.9 tok/s | 46694 ms | 128K |
| RAG | C | Runs well | 4.9 tok/s | 71837 ms | 128K |
Inference speed
LFM2.5 350M inference speed — tokens per second by GPU & Mac
Estimated decode speed (tokens/sec) for LFM2.5 350M at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~7 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.
| GPU / Mac | Memory | Quant | Speed (tok/s) | Fits? |
|---|---|---|---|---|
| 32 GB | Q4_K_M | 6.6 | Fits | |
| 24 GB | Q4_K_M | 5.6 | Fits | |
| 16 GB | Q4_K_M | 5.6 | Fits | |
| 12 GB | Q4_K_M | 5.6 | Fits | |
| 8 GB | Q4_K_M | 5.6 | Fits | |
RX 7900 XTX 24GB | 24 GB | Q4_K_M | 4.9 | Fits |
MacBook Pro M4 Max 128GB | 128 GB | Q4_K_M | 4.9 | Fits |
Mac Studio M3 Ultra 256GB | 256 GB | Q4_K_M | 4.9 | Fits |
Mac Studio M2 Ultra 128GB | 128 GB | Q4_K_M | 4.9 | Fits |
Mac Studio M1 Ultra 128GB | 128 GB | Q4_K_M | 4.9 | Fits |
MacBook Pro M4 Max 64GB | 64 GB | Q4_K_M | 4.9 | Fits |
MacBook Pro M3 Max 64GB | 64 GB | Q4_K_M | 4.9 | Fits |
MacBook Pro M1 Max 64GB | 64 GB | Q4_K_M | 4.9 | Fits |
MacBook Pro M4 Pro 48GB | 48 GB | Q4_K_M | 4.9 | Fits |
| 24 GB | Q4_K_M | 4.2 | Fits | |
| 12 GB | Q4_K_M | 4.2 | Fits |
Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.
Quantization options
How LFM2.5 350M (0.3499999940395355B params) fits at each quantization level on Intel Arc A380 6GB (6.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 0.1 GB | Low | B62 |
Q3_K_S | 3 | 0.2 GB | Low | B62 |
NVFP4 | 4 | 0.2 GB | Medium | B62 |
Q4_K_M | 4 | 0.2 GB | Medium | B62 |
Q5_K_M | 5 | 0.3 GB | High | B62 |
Q6_K | 6 | 0.3 GB | High | B62 |
Q8_0 | 8 | 0.4 GB | Very High | B63 |
F16Best for your GPU | 16 | 0.7 GB | Maximum | B63 |
Get started
Copy-paste commands to run LFM2.5 350M on your machine.
Run
lms load LFM2.5-350M && lms server startFrequently asked questions
Can Intel Arc A380 6GB run LFM2.5 350M?
Yes, Intel Arc A380 6GB can run LFM2.5 350M with a C grade (Runs well). Expected decode speed: 4.9 tok/s.
How much VRAM does LFM2.5 350M need?
LFM2.5 350M (0.3499999940395355B parameters) requires approximately 1.9 GB of memory with Q4_K_M quantization.
What is the best quantization for LFM2.5 350M?
The recommended quantization for LFM2.5 350M is Q4_K_M, which balances quality and memory efficiency.
What speed will LFM2.5 350M run at on Intel Arc A380 6GB?
On Intel Arc A380 6GB, LFM2.5 350M achieves approximately 4.9 tokens per second decode speed with a time-to-first-token of 39510ms using Q4_K_M quantization.
Can Intel Arc A380 6GB run LFM2.5 350M for coding?
For coding workloads, LFM2.5 350M on Intel Arc A380 6GB receives a C grade with 4.9 tok/s and 128K context.
What context window can LFM2.5 350M use on Intel Arc A380 6GB?
On Intel Arc A380 6GB, LFM2.5 350M can safely use up to 128K tokens of context. The model's official context limit is 128K, but available memory constrains the safe maximum.
What should I upgrade first if LFM2.5 350M feels slow on Intel Arc A380 6GB?
Prioritize bandwidth, not only capacity. If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Would CUDA be a better path than Intel Arc A380 6GB for LFM2.5 350M?
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.
Embed this result▼
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/lfm2.5-350m-on-arc-a380-6gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: