Arc Pro B60

An Arc Pro B60 runs 28 of the 34 open models tracked here at Q4_K_M with 8k context, computed on 16 October 2026. The largest is Qwen3.6 35B-A3B (MoE), needing 22.4 GB and generating at most 183 tokens per second.

Updated

Memory
24 GB VRAM
Bandwidth
456 GB/s
Board power
200 W
Released
2025
Availability
Workstation card
What it runs
28 of 34 models
At Q4_K_M with 8k context. The largest it holds is Qwen3.6 35B-A3B (MoE): 22.4 GB, at most 183 tokens per second.
Computed 16 October 2026
Best model to run
Gemma 4 12B
8.2 GB of 24 GB, about 46 tokens per second: comfortable for chat. Picked as the biggest class of model that fits with room to spare and answers at 25 tokens per second or faster, then the newest release in it.
Computed 16 October 2026

Open the Arc Pro B60 in the LLM checker

What an Arc Pro B60 runs, model by model

Arc Pro B60 (24 GB) addresses 24 GB at 456 GB/s. Every model below is at Q4_K_M with 8k of context, the setting most people actually use. Once the 5% safety margin comes off, the card has 22.8 GB to spend: memory decides what loads, bandwidth how fast it answers. Both are estimates from stated formulas, and the VRAM calculator shows the working.

On this card a model fits at or under 22.8 GB, and above 20.4 GB it is tight: it loads, but there is little left for the conversation, and a desktop on the same 24 GB can push it over. Tokens per second are single-stream estimates from memory bandwidth; ≤ marks a ceiling real runtimes fall well below.

Computed 16 October 2026

The model to actually run on it

Gemma 4 12B is the best use of this card: 8.2 GB of the 24 GB available, an estimated 46 tokens per second, comfortable for chat, and 131,072 tokens of context still available.

How this is chosen, since no benchmark is quoted: models are compared by size, a mixture-of-experts model counting at the geometric mean of its total and active parameters (a rule of thumb, not a measurement). The pick is the biggest class that fits with memory to spare and answers at 25 tokens per second or better, and within that class the most recent general-purpose release; coding and reasoning specialists are listed above but not recommended by default.

Qwen3.6 35B-A3B (MoE) is the largest model the card will hold, at 22.4 GB, but it is the wrong daily driver: filling 93% of memory leaves room for only 25,600 tokens of conversation. More parameters are not worth a context window that runs out mid-document. It is a mixture-of-experts model reading only 3B parameters per token, so it is the faster of the two at an estimated 183 tokens per second; what it gives up is the depth of a dense model that reads all of its weights for every token.

It also fits at Q8_0, in about 14.2 GB, which is worth taking whenever the memory allows: Q8 is near-lossless where Q4 costs a little accuracy.

How much context actually fits

Model size is the question people ask; context is the one that bites. The KV cache grows linearly with the conversation, so a model that loads comfortably can still run out of memory halfway through a long document. On 24 GB, the context you get is whatever the weights leave behind, which is why two cards that run the same model can feel completely different in use. These are the largest contexts this card holds, at Q4_K_M weights.

ModelMax context, FP16 KVWith Q8 KV cache
Gemma 4 12B 131,072 tokens 131,072 tokens
Qwen3 32B 9,216 tokens 18,432 tokens
Gemma 4 31B 30,720 tokens 72,704 tokens
Muse Glimmer 30B 131,072 tokens 131,072 tokens

Quantising the KV cache to Q8 roughly doubles what you can hold, at a quality cost most people never notice: Qwen3 32B on this card goes from 9,216 to 18,432 tokens. Capped at 128k tokens, or at the model's own native window where that is smaller, marked "model limit": free memory beyond that point buys nothing. Rows that hold far more context than their size suggests are hybrid, sliding-window or latent-attention models, which cache only a fraction of what a standard transformer does; each model page shows the working.

Computed 16 October 2026

Where this card stops

The first model out of reach is Llama 3.3 70B: about 45.8 GB at Q4_K_M and 8k context, against 24 GB of usable memory. Dropping to Q3_K_M would need about 37.7 GB, which still does not fit. Offloading the remainder to system RAM works and is ten to fifty times slower; it is a way to see a model run, not a way to use one.

Buy or rent

Worth it when you need 24 GB at 200 W on Intel's stack, or several cards in one Linux box under LLM Scaler. If speed matters, a used RTX 3090 reads 24 GB about twice as fast and runs CUDA, at 350 W. For occasional large models, renting by the hour costs less than a multi-card build.

Workstation cards are sold on quotes rather than shelf prices, so there is no single number to publish. Put the figure you are actually looking at, with your electricity rate and your real monthly hours, into the build vs rent calculator, which already knows this card draws 200 W under load. It returns the month owning becomes cheaper, or tells you it never does. Hours per month decides it far more often than the price does.

The honest take

Intel's 24 GB workstation card: the B580's bandwidth with twice the memory.

It holds what any 24 GB card holds, the same models as an RTX 3090 or 4090, and reads them at 456 GB/s, the same as an Arc B580 and about half a 3090. So the B60 buys capacity, not speed: larger dense models fit and generate slowly. Its software is llama.cpp through SYCL or Vulkan, Ollama through Vulkan, and Intel's LLM Scaler containers for vLLM on Linux, which are built for the B60 and B70.

What it is good at

  • 24 GB on a 200 W board.
  • Intel's LLM Scaler packages vLLM for the Arc Pro B60 and B70, with tensor and pipeline parallelism across several cards.
  • llama.cpp runs it through SYCL or Vulkan, on Linux and Windows.

What it is not

  • 456 GB/s, about half an RTX 3090: dense models that need the 24 GB generate slowly.
  • Sold through board partners in their own designs, not as an Intel card.
  • No CUDA, and Intel's older IPEX-LLM route is archived.

The thing people get wrong: It has the B580's memory bus and memory speed, so the same 456 GB/s, with twice the capacity. For a model that fits in 12 GB the B60 is no faster than the gaming card; the extra 12 GB is what you pay for.

Compared with the alternatives

  • Arc B580: 12 GB · 456 GB/s · best fit Gemma 4 12B at ~46 tok/s. Intel's 12 GB card: faster memory than an RTX 3060 12 GB, and a younger software stack.
  • Arc Pro B70: 32 GB · 608 GB/s · best fit Muse Glimmer 30B at ~25 tok/s. Intel's 32 GB workstation card: RTX 5090 capacity at 608 GB/s, on Intel's software.
  • RTX 3090: 24 GB · 936 GB/s · best fit Muse Glimmer 30B at ~38 tok/s. The value benchmark for local models, and it has been for years.

All 39 cards are compared side by side on the GPU index, and the same numbers from the model's point of view are on each model fit table. To check one specific pairing rather than read a table, use the can-I-run-it checker.

Questions

Can an Arc Pro B60 run a 70B model?
Not at Q4_K_M in one card. Llama 3.3 70B needs about 45.8 GB at 8k context and this card can address 24 GB. Your options are a smaller model, a harsher quantisation with very little context, splitting across two cards, or renting a larger one for the hours you need it.
What is the best model to run on an Arc Pro B60?
Gemma 4 12B. At Q4_K_M and 8k context it needs about 8.2 GB of the 24 GB available and generates an estimated 46 tokens per second, which is comfortable for chat. It also fits at Q8, at about 14.2 GB, which is worth taking when it fits.
How many tokens per second does an Arc Pro B60 generate?
It depends entirely on the size of the model, because generating a token means reading every active weight out of memory. At 456 GB/s and 70% efficiency, this card produces an estimated 69 tokens per second on an 8B model at Q4, and about 183 on the largest model it holds, Qwen3.6 35B-A3B (MoE). Reading speed is roughly 5 to 8 words per second, so anything above 25 feels immediate. Treat 69 as a ceiling on 456 GB/s rather than a measurement; the higher a figure, the further real runtimes fall below it.
Is 24 GB enough for running LLMs locally?
It runs 28 of the 34 models tracked here at Q4_K_M with 8k of context, up to 36B parameters. The honest test is not the model list but the context: Gemma 4 12B on this card holds about 131,072 tokens before memory runs out.
Arc Pro B60 or Arc B580 for local models?
This card holds more: 24 GB against 12 GB, so it runs 28 of these models to the Arc B580's 11. On speed, they are identical, and bandwidth is what sets chat speed.
Arc Pro B60 or Arc B580?
Both are Battlemage cards with the same memory speed and the same 456 GB/s, so a model that fits both has the same speed ceiling. The B60 has 24 GB against 12 GB and is sold through board partners. Pay for the B60 only if your models need more than 12 GB.
Arc Pro B60 or RTX 3090 for local LLMs?
Both hold 24 GB, so the same models fit. The 3090 reads memory at 936 GB/s against 456 GB/s, about twice as fast, and runs CUDA. The B60 is a current card at 200 W against the 3090's 350 W. If generation speed and tool support matter most, the 3090; if power and a new card matter more, the B60.
  • Memory: weights (parameters × bytes per parameter) + KV cache (2 × layers × KV heads × head dim × context × bytes for a standard transformer; sliding-window, hybrid and latent-attention models counted as they actually cache) + 0.5 GB runtime + 4% of weights. Full derivation in the VRAM calculator.
  • Speed: 70% × bandwidth ÷ active weight bytes, single stream, no batching, prompt processing excluded. A ceiling, not a measurement: the 8 of 28 figures marked ≤ are where real runtimes fall furthest below the number, because so few weights are read per token. See the tokens-per-second estimator.
  • Card specification (manufacturer figures): 24 GB, 456 GB/s, 200 W; see Intel's own page for this card.
  • Model architecture values come from each model's published config; the self-hosted LLM guide explains what each one changes.