live wire
AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLMAI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM
upstreambeat.ai
releaseAI

Speculators 0.6.0 brings P-EAGLE parallel drafting to vLLM

The open-source release adds an end-to-end path for training and serving draft models that predict several future tokens in one pass.

Chart of acceptance rates by depth for P-EAGLE speculative decoding.
Chart: figures from the story
By The News Desk· Sep 3, 2026the quick take — two AI hosts, this story only

Speculators 0.6.0 adds an open-source implementation of P-EAGLE, an Amazon-developed speculative-decoding algorithm that predicts several future tokens in parallel rather than drafting them one at a time. Red Hat’s release walkthrough covers data preparation, hidden-state extraction with vLLM, training, evaluation and deployment.

The practical target is drafting overhead. EAGLE-3 uses a small draft model to propose tokens sequentially before the full model verifies them. P-EAGLE adds prediction depths so that the draft model proposes multiple positions in one forward pass; the verifier checks those proposals together and accepts the valid prefix. Red Hat says that reduces sequential work, improves hardware utilization and is especially useful for long reasoning traces.

What the release adds

The P-EAGLE implementation inherits from Speculators’ existing EAGLE-3 model and introduces three main mechanisms.

Conditional Drop-token sampling reduces training memory by keeping progressively fewer positions at deeper prediction depths. The example decay keeps 70% of positions at depth one and 49% at depth two, with a 20% floor so deeper levels continue to receive training data.

P-EAGLE also uses a mask token and a learnable hidden-state tensor for future positions that do not yet have real tokens. Its embedding table is unfrozen so that the placeholder can acquire a useful representation during training. A custom flex-attention mask then lets each prediction see the causal base context and its own rollout chain without attending sideways into other speculative rollouts.

From Qwen3 training to vLLM serving

Red Hat documents a four-step Qwen3-8B workflow: prepare tokenized data, extract internal states from early, middle and late layers through vLLM, train the draft model, and serve the resulting checkpoint directly with vllm serve. The example uses 5,000 samples, four prediction depths and four H100 GPUs; the article reports roughly 50 minutes of end-to-end training.

Published results for a Qwen3 draft model show that acceptance declines with depth, as expected. Across the listed workloads, the first predicted position was accepted 74.9% of the time on average, while the average accepted length was 3.044 tokens. Math reasoning had the longest reported average at 3.820 tokens; summarization was lowest at 2.480.

Those figures are acceptance measurements, not an end-to-end latency guarantee. Workload distribution, target model and serving hardware still determine whether parallel drafting produces a useful production gain. The release matters because it makes that question testable with a reproducible training and deployment path rather than presenting P-EAGLE only as a research result.

Speculators 0.6.0 and pretrained draft models are available now through the open-source project and Red Hat AI’s model collection linked from the article.

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.