live wire
▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel
upstreambeat.ai
newsAI

vLLM extends adaptive verification to draft models without confidence heads

An online-fitted estimator lets more speculative-decoding setups trim low-value draft tokens without retraining existing checkpoints.

Before-and-after adaptive verification for draft models.
AI-generated illustration
By The News Desk· Oct 15, 2026the quick take — two AI hosts go live when you do

vLLM has extended Adaptive Verification to draft-model-based speculative decoders that do not ship with a trained confidence head, using a lightweight estimator fitted during serving. The change broadens a performance optimization that had previously been limited largely to DSpark configurations with a confidence head, according to the project's engineering write-up.

What changed

Adaptive Verification reduces work by trimming draft tokens that are unlikely to be accepted before the target model verifies them. That requires a calibrated per-token estimate of acceptance probability. Draft models such as EAGLE, MTP and DFlash, along with some DSpark checkpoints, lack the dedicated confidence head previously used to produce that estimate; adding one would require retraining the drafter.

vLLM's new approach instead applies a small logistic-regression model to the log-odds of the drafter's most likely token. It uses one slope shared across draft positions and a separate intercept for each position. The coefficients are continually refitted from accept-or-reject outcomes that the target model already produces during normal verification, allowing the estimator to adapt to a particular model pair and incoming workload without changing the checkpoint.

The implementation landed in vLLM pull request 52228. Operators enable it through enable_adaptive_verification in the speculative configuration; when a compatible draft model lacks a confidence head, vLLM selects the online estimator automatically.

What the measurements show

The project tested the estimator with MiMo-V2.5-Pro-FP4 plus DFlash, Inkling-NVFP4 plus MTP, Muse-Glimmer-30B plus DFlash2, and DeepSeek-V4-Flash plus DSpark. At concurrency 64, Adaptive Verification with the estimator improved output throughput over fixed verification at the same speculative length across all tested datasets.

On DeepSeek-V4-Flash plus DSpark, the estimator and a trained confidence head were roughly even across the measured concurrency levels. For MiMo-V2.5-Pro-FP4 plus DFlash, a configuration that lacked a confidence head, Adaptive Verification landed on the throughput-versus-interactivity frontier at five of seven tested concurrencies.

Those results do not make the estimator universally optimal. vLLM notes that a shorter fixed speculative length can still beat Adaptive Verification at the maximum speculative length for a particular concurrency. The target model's attention backend must also support variable-length verification, and the project found smaller benefits for autoregressive MTP and EAGLE speculators than for DFlash and DSpark.

The practical change is narrower but useful: existing draft checkpoints can now use workload-adaptive token trimming without a separate confidence-head training step. The work builds on Adaptive Verification contributions by Red Hat's Lucas Wilkinson and NVIDIA's Benjamin Chislett.

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.