Course3 of 9 modules live
From your laptop to hyperscale H100 clusters — how large language models are actually served, built for engineers who already know distributed systems.
Written for engineers fluent in Java, Kubernetes, AWS, Docker, distributed systems and networking. No hand-holding on those — deep on everything GPU- and inference-specific.
A request flows top-down; each layer is a module. Every optimization exists to make the bottom two layers cheaper at the top.
Production & cloud
gateway → auth → LB → scheduler → GPU cluster · AWS / GCP
The inference engine
continuous batching · paged KV cache · prefix caching · schedulers
Scaling across GPUs & nodes
tensor / pipeline / expert parallelism · NCCL · NVLink · RDMA
Hardware & optimization
SMs · Tensor Cores · HBM · the roofline · quantization · FlashAttention
Foundations
how inference works · running models locally
Continuous batching, PagedAttention, prefix caching, CUDA graphs and speculative decoding — the algorithms and data structures inside a serving engine.
continuous
batching
paged
KV cache
7 engines
compared
Tensor / pipeline / expert parallelism, NCCL collectives, and a full trace of one token generated across eight H100 GPUs.
TP/PP/EP
strategies
160
AllReduces/token
8×H100
worked example
Crossing the node boundary: RDMA, RoCE and InfiniBand, scaling 2 → 64 → 1024 GPUs, fault tolerance and KV-aware load balancing.
RDMA
kernel bypass
1024
GPUs
N+1
fault tolerance
The full request lifecycle, prefill/decode disaggregation, GPU-aware Kubernetes, and representative ChatGPT / Claude / DeepSeek serving architectures.
gateway→GPU
lifecycle
disaggregated
prefill/decode
3 stacks
reference
AWS vs GCP for inference: GPU instances, EFA / GPUDirect networking, EKS / GKE, spot economics and managed inference services.
P5 vs A3
instances
spot
economics
build/buy
framework
The optimization toolbox on one roofline: quantization, FlashAttention, KV compression, speculative decoding — and when each one pays off.
roofline
framing
FP16→INT4
quant
playbook
prioritized