In vLLM v0.23.0, vllm:prefix_cache_hits is incremented from SchedulerStats.prefix_cache_stats.hits on each logging update and observes prefix-cache token reuse for the first-party prefix cache (KV-connector prefix-cache reuse is reported by the separate vllm:external_prefix_cache_* counters).
MetricvLLM v0.23.0confidence: highverified 10 min agoverified-code
Metric
prefix_cache_hitsApplies when
PrometheusStatLogger metrics publisherV1 metrics
Evidence
vLLM v0.23.0 v1 metrics loggers.py(vllm/v1/metrics/loggers.py:1083-1088)
definesprimarysource_codecode_introspection
vLLM v0.23.0 v1 metrics stats.py(vllm/v1/metrics/stats.py:24-33)
definesprimarysource_codecode_introspection
vLLM v0.23.0 v1 metrics loggers.py(vllm/v1/metrics/loggers.py:562-588)
supportssecondarysource_codecode_introspection
Does not establish
- why reuse is high or low for a given workload
- connector/external prefix-cache reuse
Guards
vllm_version= v0.23.0metric_name=vllm:prefix_cache_hitsruntime_component=kv_cache