Tokens per Second Calculator: Latency and Throughput
Enter measured output tokens and elapsed time for one streamed request or a whole run. Compare end-to-end throughput with decode rate and request throughput.
Results
- End-to-end output throughput
- 33.667 tokens/s
- Mean inter-token latency (excludes first token)
- 20 ms
- Decode rate (reciprocal of ITL)
- 50 tokens/s
- Use measured output token counts, not words or input tokens. Aggregate throughput does not predict individual latency.
How it works
Following NVIDIA’s metric definitions, output throughput is output tokens divided by measured elapsed seconds. In single-request mode, mean inter-token latency excludes the first token. Its reciprocal is the decode rate, which differs from end-to-end throughput.
ITL = (elapsed − TTFT) / (output tokens − 1) decode rate = 1 / ITL run throughput = total output tokens / wall time request throughput = completed requests / wall time
For a run, measure wall time from the first request to the last response; do not add overlapping request latencies. Zero or one token has no inter-token interval. TTFT cannot be inferred from aggregate throughput. Results use up to three decimals with no intermediate rounding.
Worked examples
One streamed request
101 output tokens in 3 seconds, with TTFT of 1 second, give 33.667 tokens/s end-to-end. ITL is (3 − 1) / 100 = 20 ms and decode rate is 50 tokens/s.
A concurrent benchmark run
1,000 output tokens and 10 completed requests in a 5-second wall-time window give 200 tokens/s and 2 requests/s.
Frequently asked questions
Why subtract one output token for ITL?
Is decode speed the same as tokens per second?
Can I calculate TTFT from total time alone?
Should I include prompt tokens?
What if no output tokens are produced?
Sources
- NVIDIA NIM — benchmark metric definitions (checked 2026-11-14)
Last reviewed 2026-11-14. The method is written out above so you can check our math.