willitrun·ai

Can Qwen3-Coder 30B A3B Instruct run on Intel Data Center GPU Max 1550 128GB?

YES — Runs Great

S91Excellent
Estimated from fit model

Qwen3-Coder 30B A3B Instruct needs ~33.8 GB VRAM. Intel Data Center GPU Max 1550 128GB has 128.0 GB. With Q4_K_M quantization, expect ~305 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: HighStack: StandardBottleneck: Balanced
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) 33.8 GB, 304.8 tok/s, Runs well
33.8 GB required128.0 GB available
26% VRAM used

Fit status

Runs well

Decode

304.8 tok/s

TTFT

635 ms

Safe context

256K

Memory

33.8 GB / 128.0 GB

Memory breakdown

Weights18.6 GB
KV Cache1.5 GB
Runtime0.9 GB
Headroom12.8 GB

See how fast it feels

See how fast it feelsQwen3-Coder 30B A3B Instruct on Intel Data Center GPU Max 1550 128GB
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: 304.8 tok/s decode · 635ms TTFT (warm) · 762 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 well304.8 tok/s350 ms256K
CodingSRuns well304.8 tok/s635 ms256K
Agentic CodingSRuns well304.8 tok/s924 ms256K
ReasoningSRuns well304.8 tok/s751 ms256K
RAGSRuns well304.8 tok/s1155 ms256K

Inference speed

Qwen3-Coder 30B A3B Instruct inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Qwen3-Coder 30B A3B Instruct at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~182 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 / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M181.6Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M115.8Offloads
RX 7900 XTX 24GB
24 GBQ4_K_M104.5Offloads
NVIDIARTX 3090 24GB
24 GBQ4_K_M99.1Offloads
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M84.2Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M70.2Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M66.5Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M52.0Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M52.0Fits
MacBook Pro M3 Max 64GB
64 GBQ4_K_M36.3Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M33.3Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M32.7Too big
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M31.8Fits
NVIDIARTX 4070 12GB
12 GBQ4_K_M11.4Too big
NVIDIARTX 3060 12GB
12 GBQ4_K_M7.2Too big
NVIDIARTX 4060 8GB
8 GBQ4_K_M4.5Too big

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 Qwen3-Coder 30B A3B Instruct (30.5B params) fits at each quantization level on Intel Data Center GPU Max 1550 128GB (128.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
11.9 GB
LowA82
Q3_K_S
3
14.9 GB
LowA82
NVFP4
4
17.1 GB
MediumA82
Q4_K_M
4
18.6 GB
MediumA82
Q5_K_M
5
22.0 GB
HighA82
Q6_K
6
25.0 GB
HighA83
Q8_0
8
32.6 GB
Very HighA84
F16Best for your GPU
16
62.5 GB
MaximumS89

Get started

Copy-paste commands to run Qwen3-Coder 30B A3B Instruct on your machine.

Run

ollama run qwen3-coder

Your hardware

More models your Intel Data Center GPU Max 1550 128GB can run

ModelParamsGradeDecodeCapabilities
MistralDevstral 2 123B Instruct123BS29.2 tok/s

Frequently asked questions

Can Intel Data Center GPU Max 1550 128GB run Qwen3-Coder 30B A3B Instruct?

Yes, Intel Data Center GPU Max 1550 128GB can run Qwen3-Coder 30B A3B Instruct with a S grade (Runs well). Expected decode speed: 304.8 tok/s.

How much VRAM does Qwen3-Coder 30B A3B Instruct need?

Qwen3-Coder 30B A3B Instruct (30.5B parameters) requires approximately 33.8 GB of memory with Q4_K_M quantization.

What is the best quantization for Qwen3-Coder 30B A3B Instruct?

The recommended quantization for Qwen3-Coder 30B A3B Instruct is Q4_K_M, which balances quality and memory efficiency.

What speed will Qwen3-Coder 30B A3B Instruct run at on Intel Data Center GPU Max 1550 128GB?

On Intel Data Center GPU Max 1550 128GB, Qwen3-Coder 30B A3B Instruct achieves approximately 304.8 tokens per second decode speed with a time-to-first-token of 635ms using Q4_K_M quantization.

Can Intel Data Center GPU Max 1550 128GB run Qwen3-Coder 30B A3B Instruct for coding?

For coding workloads, Qwen3-Coder 30B A3B Instruct on Intel Data Center GPU Max 1550 128GB receives a S grade with 304.8 tok/s and 256K context.

What context window can Qwen3-Coder 30B A3B Instruct use on Intel Data Center GPU Max 1550 128GB?

On Intel Data Center GPU Max 1550 128GB, Qwen3-Coder 30B A3B Instruct can safely use up to 256K tokens of context. The model's official context limit is 256K, but available memory constrains the safe maximum.

What should I upgrade first if Qwen3-Coder 30B A3B Instruct feels slow on Intel Data Center GPU Max 1550 128GB?

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.

Would CUDA be a better path than Intel Data Center GPU Max 1550 128GB for Qwen3-Coder 30B A3B Instruct?

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 Data Center GPU Max 1550 128GBSee all hardware for Qwen3-Coder 30B A3B Instruct
Embed this result

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

<iframe src="https://willitrunai.com/embed/qwen-3-coder-30b-a3b-on-max-1550-128gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: