Can Qwen3.5 27B run on Intel Arc Pro B60 24GB?

YES — With Offload

C48Usable

○Estimated from fit model

Qwen3.5 27B needs ~22.9 GB VRAM. Intel Arc Pro B60 24GB has 24.0 GB. With Q4_K_M quantization, expect ~15 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: MediumStack: StandardBottleneck: Balanced

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) — 22.9 GB, 15.0 tok/s, Runs with offload

22.9 GB required24.0 GB available

95% VRAM used

Fit status

Runs with offload

Decode

15.0 tok/s

TTFT

12949 ms

Safe context

21K

Memory

22.9 GB / 24.0 GB

Memory breakdown

Weights16.5 GB

KV Cache3.2 GB

Runtime0.9 GB

Headroom2.4 GB

See how fast it feels

See how fast it feelsQwen3.5 27B on Intel Arc Pro B60 24GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API.

When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed.

Key benefits of running locally:
 - Full privacy: your prompts never leave your machine
 - No per-token cost or rate limits
 - Works offline once the model is downloaded
 - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb:

 Model size Q4 (4-bit) Q8 (8-bit) FP16
 7B params ~4.3 GB ~7.5 GB ~14 GB
 13B params ~7.9 GB ~13.9 GB ~26 GB
 70B params ~42.7 GB ~74.9 GB ~140 GB

Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 15.0 tok/s decode · 12.9s TTFT (warm) · 37 tok/s prefill

What limits this setup

The raw memory story may look fine, but the software ecosystem is still a constraint here.

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

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

Workload	Grade	Fit	Decode	TTFT	Context
Chat	C	Tight fit	15.0 tok/s	7063 ms	21K
Coding	C	Runs with offload	15.0 tok/s	12949 ms	21K
Agentic Coding	D	Very compromised	9.6 tok/s	29223 ms	21K
Reasoning	C	Runs with offload	15.0 tok/s	15304 ms	21K
RAG	D	Very compromised	9.6 tok/s	36529 ms	21K

Quantization options

How Qwen3.5 27B (27B params) fits at each quantization level on Intel Arc Pro B60 24GB (24.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	10.5 GB	Low	C50
Q3_K_S	3	13.2 GB	Low	C50
NVFP4	4

Get started

Copy-paste commands to run Qwen3.5 27B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
 --hf-repo "unsloth/Qwen3.5-27B-GGUF" \
 --hf-file "Qwen3.5-27B-GGUF-Q4_K_M.gguf" \
 -c 4096 -ngl 99

Upgrade options