Skip to playbook content
Browse all chapters
Chapter 018 min readReviewed 31 August 2026

Start with constraints, not a GPU name

Turn a workload, service target, and operating envelope into a benchmarkable shortlist.

On this page
  1. The five gates
  2. Build a shortlist
  3. Decision record
The decision order

Five gates prevent an expensive shortcut

A GPU decision is valid only after the workload passes all five gates. A famous SKU can fail on fit, software, fabric, facility, or unit cost.

01Fit

Weights + state + KV/activations + workspace + headroom

02Math

Required precision, kernels, codecs, and software support

03Service

TTFT, token cadence, throughput, quality, and reliability

04Topology

One GPU, linked node, or multi-node fabric - and the physical envelope

05Economics

Cost per successful unit at the SLO, including idle and failed work

A

Workload envelope

Model or kernel, precision, input/output shape, batch and concurrency, context length, data movement, duration, and failure tolerance.

B

Service contract

p50/p95/p99 latency, useful throughput, quality gates, deadline, availability, recovery point, and regional or data-governance limits.

C

Operating envelope

Framework and engine, driver matrix, rack or cloud shape, quota, interconnect, power, cooling, team skill, and purchase term.

Guided path

Build a benchmark shortlist

The worksheet deliberately stops at a candidate lane. It does not manufacture a precision recommendation from a few dropdowns.

Interactive worksheet · shortlist only

Translate constraints into a test plan

Use the estimated resident footprint: weights, KV or activations, engine workspace, and operating headroom - not the checkpoint file alone.

1 · Workload
2 · Resident footprint
3 · First priority
4 · Software constraint
Candidate laneH100 / A100 80 GB
Topology
Start with one GPU per replica; add data-parallel replicas only after the single-replica benchmark passes.
Proof
Sweep concurrency until p95 TTFT or TPOT fails, then price the highest SLO-compliant point.
Guardrail
Optimize p95/p99, not only the single-request best case; queueing and mixed prompt lengths decide production latency.

This is not a benchmark or purchase recommendation. Verify exact SKU, software version, region, power envelope, and production trace.

Required artifact

Write the decision before requesting quotes

A one-page record keeps benchmark results, provider quotes, and architecture tradeoffs comparable.

FieldMinimum evidenceReject when
WorkloadVersioned model/kernel, real input and output distributionsOnly a model name or parameter count is supplied
MemoryMeasured peak residency plus rollout/failure headroomCheckpoint size is treated as total memory
PerformanceSLO goodput with p95/p99 latency and errorsOnly peak FLOPS or unconstrained tokens/s is shown
TopologyExact GPU form factor, links, host, NICs, placementThe quote says only “8× H100”
SoftwarePinned driver, framework, engine, model and precision matrixSupport is inferred from architecture name
CostFully loaded cost per useful output or accepted stepComparison stops at $/GPU-hour
RiskCapacity, interruption, restart, upgrade, and fallback testAvailability or recovery is assumed