VOOZH about

URL: https://willitrunai.com/can-run/mistral-small-3.2-24b-on-arc-a770-16gb


Can Mistral Small 3.2 24B run on Intel Arc A770 16GB?

YES — With NVFP4

A71Great
Estimated from fit model

Mistral Small 3.2 24B needs ~18.7 GB VRAM. Intel Arc A770 16GB has 16.0 GB. With NVFP4 quantization, expect ~12 tok/s.

Runtime: OllamaCapacity: OffloadBandwidth: MediumStack: BasicBottleneck: 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.

Mistral Small 3.2 24B at Q4_K_M needs 19.9 GB — too much for Intel Arc A770 16GB (16.0 GB). Runs at NVFP4 (18.7 GB) with medium quality. 3 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 19.9 GB, exceeds 16.0 GB available
19.9 GB required16.0 GB available
124% VRAM needed

3.9 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

8.8 tok/s

TTFT

22036 ms

Safe context

4K

Memory

19.9 GB / 16.0 GB

Offload

20%

Memory breakdown

Weights14.6 GB
KV Cache2.4 GB
Runtime1.2 GB
Headroom1.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsMistral Small 3.2 24B on Intel Arc A770 16GB
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: 8.8 tok/s decode · 22.0s TTFT (warm) · 22 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 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.

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
ChatAVery compromised9.3 tok/s11308 ms4K
CodingFToo heavy8.2 tok/s23689 ms4K
Agentic CodingFToo heavy6.4 tok/s43970 ms4K
ReasoningFToo heavy8.2 tok/s27996 ms4K
RAGFToo heavy6.4 tok/s54962 ms4K

Quantization options

How Mistral Small 3.2 24B (24B params) fits at each quantization level on Intel Arc A770 16GB (16.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
9.4 GB
LowA85
Q3_K_SBest for your GPU
3
11.8 GB
LowA84

Get started

Copy-paste commands to run Mistral Small 3.2 24B on your machine.

Run

ollama run mistral-small3.2

Upgrade options

Hardware that runs Mistral Small 3.2 24B well

👁 Intel
Intel Arc Pro B60 24GBBudget pick
24 GB VRAM (+8)
A
Makes the model fit on the accelerator instead of staying completely out of reach.18.1 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.

~$599 MSRP

👁 NVIDIA
RTX 5090 32GBBiggest leap
32 GB VRAM (+16)1792 GB/s (+1232)
S
Makes the model fit on the accelerator instead of staying completely out of reach.88.2 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.

~$1,999 MSRP

👁 Intel
Intel Data Center GPU Max 1550 128GBBest value
128 GB VRAM (+112)3200 GB/s (+2640)
A
Makes the model fit on the accelerator instead of staying completely out of reach.148 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.

~$15,000 MSRP

👁 Intel
Gaudi 3 128GBIntel upgrade
128 GB VRAM (+112)3700 GB/s (+3140)
A
Makes the model fit on the accelerator instead of staying completely out of reach.190.2 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.

~$15,000 MSRP

Frequently asked questions

See all results for Intel Arc A770 16GBSee all hardware for Mistral Small 3.2 24B
NVFP4
4
13.4 GB
Medium
F0
Q4_K_M
4
14.6 GB
MediumF0
Q5_K_M
5
17.3 GB
HighF0
Q6_K
6
19.7 GB
HighF0
Q8_0
8
25.7 GB
Very HighF0
F16
16
49.2 GB
MaximumF0