Can Devstral Small 1.1 run on Intel Arc Pro B50 16GB?

YES — With NVFP4

A75Great
Estimated from fit model

Devstral Small 1.1 needs ~18.4 GB VRAM. Intel Arc Pro B50 16GB has 16.0 GB. With NVFP4 quantization, expect ~6 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.

Devstral Small 1.1 at Q4_K_M needs 19.6 GB — too much for Intel Arc Pro B50 16GB (16.0 GB). Runs at NVFP4 (18.4 GB) with medium quality. 3 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 19.6 GB, exceeds 16.0 GB available
19.6 GB required16.0 GB available
123% VRAM needed

3.6 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

4.5 tok/s

TTFT

43039 ms

Safe context

4K

Memory

19.6 GB / 16.0 GB

Offload

20%

Memory breakdown

Weights14.6 GB
KV Cache2.4 GB
Runtime0.9 GB
Headroom1.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsDevstral Small 1.1 on Intel Arc Pro B50 16GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 4.5 tok/s decode · 43.0s TTFT (warm) · 11 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 compromised (needs ~1.9 GB host RAM)5.1 tok/s20587 ms4K
CodingFToo heavy4.5 tok/s43039 ms4K
Agentic CodingFToo heavy3.5 tok/s79558 ms4K
ReasoningFToo heavy4.5 tok/s50864 ms4K
RAGFToo heavy3.5 tok/s99448 ms4K

Quantization options

How Devstral Small 1.1 (24B params) fits at each quantization level on Intel Arc Pro B50 16GB (16.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
9.4 GB
LowS91
Q3_K_SBest for your GPU
3
11.8 GB
LowS90
NVFP4
4
13.4 GB
MediumF0
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

Get started

Copy-paste commands to run Devstral Small 1.1 on your machine.

Run

lms load Devstral-Small-2507 && lms server start

アップグレードオプション

Devstral Small 1.1を快適に動かすハードウェア

Frequently asked questions

Can Intel Arc Pro B50 16GB run Devstral Small 1.1?

Yes, Intel Arc Pro B50 16GB can run Devstral Small 1.1 at NVFP4 quantization (Very compromised (needs ~1.7 GB host RAM)). The recommended Q4_K_M requires 19.6 GB which exceeds available memory, but at NVFP4 it needs only 18.4 GB. Expected decode speed: 5.9 tok/s.

How much VRAM does Devstral Small 1.1 need?

Devstral Small 1.1 (24B parameters) requires approximately 19.6 GB at Q4_K_M quantization. On Intel Arc Pro B50 16GB, it fits at NVFP4 using 18.4 GB.

What is the best quantization for Devstral Small 1.1?

The recommended quantization is Q4_K_M, but on Intel Arc Pro B50 16GB the best fitting quantization is NVFP4, which uses 18.4 GB.

What speed will Devstral Small 1.1 run at on Intel Arc Pro B50 16GB?

On Intel Arc Pro B50 16GB, Devstral Small 1.1 achieves approximately 5.9 tokens per second decode speed with a time-to-first-token of 33075ms using NVFP4 quantization.

Can Intel Arc Pro B50 16GB run Devstral Small 1.1 for coding?

For coding workloads, Devstral Small 1.1 on Intel Arc Pro B50 16GB receives a F grade with 4.5 tok/s and 4K context.

What context window can Devstral Small 1.1 use on Intel Arc Pro B50 16GB?

On Intel Arc Pro B50 16GB, Devstral Small 1.1 can safely use up to 4K tokens of context at NVFP4 quantization. The model's official context limit is 131K, but available memory constrains the safe maximum.

What should I upgrade first if Devstral Small 1.1 feels slow on Intel Arc Pro B50 16GB?

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.

Would CUDA be a better path than Intel Arc Pro B50 16GB for Devstral Small 1.1?

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.

See all results for Intel Arc Pro B50 16GBSee all hardware for Devstral Small 1.1
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/devstral-small-2507-on-arc-pro-b50-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: