Models
Inference and serving systems
Batching, the KV cache, prefix caching, schedulers and how to measure a serving engine.
32 of 30 planned
L1 2L2 16L3 11L4 3
RolesInference Engineering
- The two phases of one request
- Why 255 tokens per second is a slogan
- Cached tokens at zero with a stable template
- Choose tensor, pipeline or data parallelism
- How many users fit in the KV pool
- How speculative decoding keeps the output the same
- One token budget instead of two phases
- Read the GPU clock before the throughput
- Read three scheduler log lines
- Sleep, wake and weight updates for an RL loop
- Temperature zero gave two different answers
- The knee that the prefix cache hid
- Two clients, two numbers, one server
- What an FP8 KV cache buys and costs
- What many LoRA adapters cost one server
- Why one ID at the top of a prompt kills the cache
- Why the KV cache is a pool of 16-token blocks
- Why the shared part of the prompt goes first
- A larger token budget at low load
- Acceptance by draft position, tokens per pass
- An admission cap decides who waits
- Pick a concurrency cap when throughput keeps rising
- Pick the EAGLE3 draft depth for your concurrency
- Should the prefill chunk be smaller
- Speculation won the benchmark and lost in production
- Two data-parallel copies, less output than one card
- What determinism costs a live server
- When an FP8 checkpoint pays
- When prefill-decode disaggregation pays
- A split-server benchmark that counted empty answers
- Design a chat service on a fleet of L4 cards
- Same throughput, two choices at a full pool
No item matches this level.
Taught in
The answers on this card come from these lessons and manuals.
- KV Cache, Flash Attention & Inference Optimization
- Quantization: Making Models Fit
- Inference Optimization
- Prompt Caching and Context Caching
- Serving Engine Internals
- EAGLE-3 Speculative Decoding in Production
- Prefix-Cache Serving
- Hardware-Specialized Inference Compilation
- Inference Metrics
- Production Quantization
- Production Serving Stack
- Load Testing LLM APIs