975B

parameters, served over plain Gigabit Ethernet.

CascadiaIntel

Serving a 975B-parameter model across eleven Intel AI PCs

Alongside Intel, we sharded Thinking Machines’ Inkling across off-the-shelf PCs and served it at up to 60 tok/s of aggregate throughput.

Share this case study
Intel Core Ultra PCs

11

Peak aggregate throughput

60.29tok/s

Concurrent streams at peak

88

At a glance

Partner
Intel
Industry
Technology
Use case
Frontier-scale inference on client hardware
Model
Inkling (975B), Thinking Machines
Hardware
11× Core Ultra X7 358H, Arc B390 iGPU, 64GB RAM each
Network
Gigabit Ethernet

Key takeaways

  1. 01

    Frontier-scale open-weight models run on ordinary PCs.

    A small fleet of regular machines held and served all 975B of Inkling’s parameters.

  2. 02

    Throughput grows with users.

    Aggregate throughput climbed with concurrency and peaked at 60.29 tok/s with 88 streams at once.

  3. 03

    No data-center networking infrastructure needed.

    The machines connected over plain Gigabit Ethernet, with no InfiniBand or other high-speed interconnect.

The challenge

No single PC can hold a model of this size.

Open-weight models keep getting bigger. Inkling by Thinking Machines has almost 1T parameters, and models of that size are normally trained and served on data-center hardware.

Pooling the memory and compute of several machines makes it possible in principle, but getting a model this large to run efficiently across a fleet of ordinary PCs is the hard part. Intel wanted to know whether its new Core Ultra machines were capable of doing it.

Intel is focused on engineering the next wave of computing, where AI workloads are distributed, efficient, and closer to where data is generated. We’re excited to be working with Cascadia to enable consumer/enterprise AI PCs to run models previously impossible and help bring efficient distributed AI to more environments.
Dennis LuoSenior Director / General Manager, Worldwide Developer Relations & Innovation, Intel

The approach

Split the model into six-layer shards, one per machine.

We ran Inkling on eleven Intel Core Ultra X7 PCs, each with an Arc B390 iGPU and 64GB of RAM (704GB in total), connected over Gigabit Ethernet.

The setup11 machines · 704GB
Machines
11
CPU
Intel Core Ultra X7 358H
GPU
Intel Arc B390 integrated graphics
Memory
64GB per machine, 704GB in total
Network
Gigabit Ethernet
Runtime
Cascadia (Rust + OpenVINO)

Inkling is a sparse Mixture-of-Experts model with 41B active parameters per token across 66 decoder layers. Cascadia split those layers into six-layer shards, one per machine: Machine 0 holds the embeddings and the first six layers, Machines 1–9 each hold six sparse layers, and Machine 10 runs the last six and picks the next token.

Pipeline diagram: Inkling’s 66 layers split across eleven Intel AI PCs in six-layer shards, with the next token returning to Machine 0.
Fig. 01Inkling’s 66 layers, sharded six per machine across the fleet.

A custom MoE engine for Core Ultra

On each machine, Cascadia splits the work between the CPU and the iGPU. The CPU handles attention, routing tokens to experts, and request tracking; the iGPU runs the expert calculations and compressed projections using OpenVINO’s fused MoE operations, while Cascadia keeps control of routing.

Expert weights are INT4, attention projections and the output head are INT8, and the residual stream stays at FP32.

8.1 → 4.5ms

Time per dense layer, down from about 8.1ms, after we re-expressed Inkling’s two dense layers as always-on expert slices on the same fused path.

The results

Throughput climbed with every user, peaking at 60.29 tok/s.

Each request generated 128 tokens with greedy decoding at Cascadia’s default 1,024-token context. Aggregate throughput climbed with concurrency and peaked at 60.29 tok/s with 88 concurrent streams.

Aggregate decode throughput by concurrent streams

tok/s · 128 tokens per request · greedy decoding

  • 1 stream7.96
  • 8 streams18.60
  • 32 streams38.31
  • 64 streams53.60
  • 88 streams60.29Peak
  • 176 streams57.72
Fig. 02Selected runs. The full table, with whole-phase throughput and time to first token, is in the paper.

Single-stream speed was modest at roughly 5–10 tok/s, which makes this setup best suited to multi-user serving and background work. The point was never single-user speed: it was proving that an organization’s existing fleet of PCs can serve a model this large at all.

Resources

Read the full report.

The paper, the engineering write-up and the source code are all linked below.

Research with Intel

The methods behind the numbers, co-authored with Intel engineers.

  • Paper · October 2026

    Cascadia: Resident 975B MoE Inference on Eleven AI PCs

    Tate Berenbaum, Matias Parij (Community Labs) · Muthaiah Venkatachalam (Intel)

    Read the paper
  • Paper · September 2026

    Cascadia: A Control-Plane-Free Alternative to Hyperconverged AI Infrastructure

    Matias Parij, Pawan Paudel, Tate Berenbaum (Community Labs) · Muthaiah Venkatachalam (Intel)

    Read the paper
  • Paper · August 2026

    Pre-Compiled Pipeline Shards for Distributed LLM Inference on Intel AI PC Fleets

    Tate Berenbaum (Community Labs) · Muthaiah Venkatachalam (Intel)

    Read the paper

Private AI on your own machines, in a week.

We set up your first model on your network in under a week. Prompts and data never leave the building, and you pay per machine, never per token.

See it run on hardware like yours.

Book a demo

Check the engineering first.

See our research