You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: remove mid-stream TPOT predictions from predicted-latency producer
The mid-stream prediction path in processTokenForLatencyPrediction was
observability-only and low quality: computed from the scheduling-time
metrics snapshot, averaged together with the scheduling-time TPOT
prediction, and the only remaining caller of buildPredictionRequest
using the scraped RunningRequestsSize gauge (train/serve inconsistency).
avgPredictedTPOT now reduces to the scheduling-time prediction, which
is the meaningful predicted-vs-actual comparison.
The decodeTokenSampler becomes dead code with this removal (its only
remaining consumer was the removed prediction path) and is deleted,
along with the write-only tpotObservations field. The samplingMean and
maxDecodeTokenSamplesForPrediction config parameters are kept in Config
for compatibility with existing configs (the strict decoder would
otherwise reject them) but are ignored, with a deprecation log when set.
Fixes#2016
Signed-off-by: Michele Campi <215741962+MicheleCampi@users.noreply.github.com>
# Conflicts:
# pkg/epp/framework/plugins/requestcontrol/dataproducer/predictedlatency/requestcontrol_hooks.go
log.FromContext(handle.Context()).Info("Deprecated: samplingMean and maxDecodeTokenSamplesForPrediction are ignored; mid-stream TPOT predictions were removed")
logger.V(logutil.DEBUG).Info("Initialized token sampler for first token", "request_id", requestID, "next_prediction_token", predictedLatencyCtx.decodeTokenSampler.getNextSampleToken())
0 commit comments