In vLLM v0.23.0, `decode_time` is computed as `req_stats.last_token_ts` - `req_stats.first_token_ts`; the source comment describes the decode interval as from first `NEW_TOKEN` to last `NEW_TOKEN` and says any preemptions during decode are included.

MetricvLLM v0.23.0confidence: highverified 3 hr agoverified-code

V1 metricsIterationStats.update_from_finished_request finished-request accounting

vLLM v0.23.0 v1 metrics stats.py(vllm/v1/metrics/stats.py:446-448)

definesprimarysource_codecode_introspection

Pinned release-tag source snapshot; re-check if target phase-1 release changes or metrics API compatibility becomes customer-facing.

In vLLM v0.23.0, decode_time is computed as req_stats.last_token_ts - req_stats.first_token_ts; the source comment describes the decode interval as from first NEW_TOKEN to last NEW_TOKEN and says any preemptions during decode are included.