liveBook · Manning

Time per output token

As explained in Domain-Specific Small Language Models

The time required to generate each additional output token during response generation.

Time per output token (TPOT) measures how long an inference system takes to generate each output token for each active user. It complements time to first token (TTFT), latency, and throughput when assessing production serving performance. section 4.2

Use TPOT to reason about generation speed and deployment constraints:

  • Distinguish TPOT from TTFT: TPOT describes ongoing token generation, while TTFT describes the delay before the first token appears. section 4.2
  • Interpret complete-response latency through both TTFT and TPOT; evaluate throughput separately across users and requests. section 4.2
  • Account for GPU utilization, memory constraints, KV-cache capacity, batching, and optimization when targeting TPOT and other serving objectives. section 4.2 section 4.4

GPT-Neo on a T4 GPU

A GPT-Neo inference estimate on a T4 GPU produces about one token every 36 milliseconds, illustrating TPOT as an observable generation-time measure. section 4.4

How Domain-Specific Small Language Models covers it

How deep it goes
Defines TPOT and relates it to serving metrics, but stops short of presenting a standalone measurement procedure.
Examples
Uses GPT-Neo on a T4 GPU, estimating approximately one generated token every 36 milliseconds.
What you can do after
Evaluate serving performance by distinguishing ongoing token speed from first-token delay, complete-response latency, and aggregate throughput.
How it connects
Connects TPOT with TTFT, latency, throughput, GPU utilization, KV cache, dynamic batching, and quantization.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Domain-Specific Small Language Models. The section links point to the parts of the book it draws on.