INFERENCE ENGINEERING

SCENE 04 / 24 · HARDWARE MICRO-ARCHITECTURE & SILICON

CPU, GPU, TPU, LPU

Every substrate makes a different bet on parallelism, memory and flexibility.

PEAK TFLOPS989 TFMEMORY BANDWIDTH3.35 TB/s · 80 GB on-packageThousands of cores + Tensor Cores; the general-purpose accelerator.

Compute and bandwidth rarely peak together. The LPU's 80 TB/s SRAM fabric exists precisely to keep a deterministic pipeline fed; the GPU trades some of that for flexibility.

ARCHITECTURE & FORMULATIONModule 2: Hardware Micro-Architecture & Silicon Substrates

Five substrates, five bets on parallelism

CPUs, GPUs, TPUs, LPUs and inference ASICs all execute the same matmuls with radically different economics. Each substrate is a bet: flexibility (CPU), generality (GPU), dense systolic throughput (TPU), deterministic SRAM-resident scheduling (LPU), or cost-per-token within one vendor's cloud (Inferentia).

The Flexibility Tax

General-purpose silicon pays for branchy, irregular workloads with control overhead. Specialized silicon recovers that overhead as latency — until the model changes.

Memory Placement Is the Real Spec

The LPU's headline number is not FLOPs, it is 230 GB of on-die SRAM: weights stay resident and the memory wall disappears. HBM parts rent bandwidth instead.

Software Gravity

The GPU wins in production less on peak specs than on ecosystem: kernels, compilers, and a decade of framework integration. An ASIC without a compiler story is a benchmark trophy.

MATHEMATICAL FORMULATION · BANDWIDTH-CENTRIC COMPARISON
t_token ≈ weights_bytes / BW (H100: 14 GB / 3.35 TB/s ≈ 4.2 ms; LPU-class: SRAM-resident)

Decode time is weight streaming time. Substrates compete on bytes/s first and FLOPs second, which is why the LPU's 80 TB/s fabric beats the H100's 989 TF for small-batch decode.

REAL-WORLD PRODUCTION ENGINEERING
  • Groq's LPU schedules the entire model deterministically at compile time — no warp schedulers, no caches, no variance.
  • AWS Inferentia competes on $/token inside EC2, not on flexibility; model portability is the price.
Agent-native web · research mode

Experimental WebMCP · evolving community-group draft, not a W3C Standard or on the Standards Track.

Native status: Initializing. Registered: none

DOM → inferred capabilities · WebMCP → declared capabilities. Tools read real CUDA/Inference Atlas content. Calls may highlight temporary UI state. No backend or remote telemetry.

Local harness verifies application logic; it does not demonstrate native discovery or a browser agent.

Input schema
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

Local log: last 100 calls while this panel is open. Inputs may contain personal text; review before sharing.

[]