VOOZH about

URL: https://willitrunai.com/can-run/smollm3-3b-on-arc-a370m-4gb


Can SmolLM3 3B run on Intel Arc A370M 4GB?

YES — With Q3_K_S

C41Usable
Estimated from fit model

SmolLM3 3B needs ~4.7 GB VRAM. Intel Arc A370M 4GB has 4.0 GB. With Q3_K_S quantization, expect ~20 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: Very lowStack: StandardBottleneck: Host offload
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.

SmolLM3 3B at Q4_K_M needs 5.1 GB — too much for Intel Arc A370M 4GB (4.0 GB). Runs at Q3_K_S (4.7 GB) with low quality. 2 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 5.1 GB, exceeds 4.0 GB available
5.1 GB required4.0 GB available
127% VRAM needed

1.1 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

14.6 tok/s

TTFT

13260 ms

Safe context

7K

Memory

5.1 GB / 4.0 GB

Offload

20%

Memory breakdown

Weights1.8 GB
KV Cache2.0 GB
Runtime0.9 GB
Headroom0.4 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsSmolLM3 3B on Intel Arc A370M 4GB
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: 14.6 tok/s decode · 13.3s TTFT (warm) · 37 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 20% 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.

Best improvement path

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.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatBRuns with offload (needs ~0 GB host RAM)22.9 tok/s4616 ms7K
CodingFToo heavy13.6 tok/s14254 ms7K
Agentic CodingFToo heavy7.4 tok/s38240 ms7K
ReasoningFToo heavy14.6 tok/s15671 ms7K
RAGFToo heavy7.4 tok/s47800 ms7K

Quantization options

How SmolLM3 3B (3B params) fits at each quantization level on Intel Arc A370M 4GB (4.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
1.2 GB
LowB63
Q3_K_S
3
1.5 GB
LowB63
NVFP4
4

Get started

Copy-paste commands to run SmolLM3 3B on your machine.

Run

lms load SmolLM3-3B && lms server start

Upgrade options

Hardware that runs SmolLM3 3B well

👁 Intel
Intel Arc A380 6GBBudget pick
6 GB VRAM (+2)186 GB/s (+74)
B
Makes the model fit on the accelerator instead of staying completely out of reach.42 tok/s decode

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.

~$139 MSRP

👁 Intel
Intel Arc A580 8GBBest value
8 GB VRAM (+4)512 GB/s (+400)
B
Makes the model fit on the accelerator instead of staying completely out of reach.42 tok/s decode

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.

~$179 MSRP

👁 Intel
Intel Arc B570 10GBIntel upgrade
10 GB VRAM (+6)380 GB/s (+268)
B
Makes the model fit on the accelerator instead of staying completely out of reach.42 tok/s decode

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.

~$219 MSRP

Frequently asked questions

See all results for Intel Arc A370M 4GBSee all hardware for SmolLM3 3B
1.7 GB
Medium
B63
Q4_K_MBest for your GPU
4
1.8 GB
MediumB63
Q5_K_M
5
2.2 GB
HighF0
Q6_K
6
2.5 GB
HighF0
Q8_0
8
3.2 GB
Very HighF0
F16
16
6.1 GB
MaximumF0

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.