Schema.ai· vLLM
vLLM official site ↗vLLM v0.23.0Sign up

In vLLM v0.23.0, inference_time is computed as req_stats.last_token_ts - req_stats.scheduled_ts; the source comment describes the inference interval as from first SCHEDULED to last NEW_TOKEN and says any preemptions during prefill or decode are included.

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

Metric

request_inference_time_seconds

Applies when

V1 metricsIterationStats.update_from_finished_request finished-request accounting

Evidence

vLLM v0.23.0 v1 metrics stats.py(vllm/v1/metrics/stats.py:450-452)
definesprimarysource_codecode_introspection

Does not establish

  • typical or healthy inference-time durations (workload-dependent)
  • how much of a given inference_time observation is attributable to preemptions
  • inference interval semantics in vLLM versions other than v0.23.0

Guards

  • vllm_version = v0.23.0
  • metric_name = vllm:request_inference_time_seconds
  • runtime_component = scheduler

Freshness

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