vLLM 0.33 adds FLy lossy speculative verifier, off by default
11/05/2026 — 11/05, 22:20·1 sources (all)·1 reports (all)
Key takeaways
- vLLM 0.33.0 ships FLy, an optional speculative-decoding verifier that deliberately accepts some draft tokens the target model would reject.…
Background & analysis
vLLM 0.33.0, released on PyPI on 2026-11-02, ships with FLy, a speculative decoding verifier that is available as an opt-in feature. FLy deliberately accepts some draft tokens that the target model would have rejected. The PR states plainly that the verifier does not preserve the target distribution and may reduce output quality. Standard verification remains the default setting, so users have to switch it on explicitly if they want FLy's behavior.
According to the PR, FLy delivers decode throughput of 1.041x to 1.310x compared with standard speculative decoding across all 48 model, platform, and batch combinations tested, with minimum accuracy retention of 96.3%. No combination in the reported data fell below that threshold.
In standard speculative decoding, a smaller drafter proposes K tokens first, and the target model verifies them in a single forward pass. Verification stops at the first rejected token, and the accept/reject rule is constructed so that the output distribution matches what the target model would have produced on its own. FLy loosens that constraint by deliberately admitting draft tokens the target would normally discard, trading strict distributional fidelity for higher decode throughput.
The feature ships in optional mode rather than as a default replacement, and the material provides no further comparative data on FLy versus standard verification beyond the figures stated in the PR. Whether broader benchmarks or real-world deployments behave differently remains unreported here.
AI-generated from 1 reports · updated 5 hours ago
- Heat index
- 85
- All sources
- 1
- All reports
- 1
- First seen
- 6 hours ago
Reports on this story headlines open the original
vLLM 0.33.0 ships FLy, an opt-in speculative decoding verifier that deliberately accepts some draft tokens the target model would have rejected. The PR states it does not preserve the target distribution and may reduce output quality, while standard verification remains the default. The PR reports decode throughput of 1.041x to 1.310x over standard speculative decoding across all 48 model, platform and batch configurations, with minimum accuracy retention of 96.3%.
DEV Community · AIAI score 58
Other stories people are talking about
- Heat index 840OpenAI ships Images 2.6 with GIF and SVG output15 sources
- Heat index 675OpenAI says its cyber model pipeline confirmed 1,724 Linux kernel flaws and generated 948 privilege-escalation exploits11 sources
- Heat index 642RisingOpenAI GPT-5.6 Brings Major Agentic and Computer Use Upgrades13 sources
- Heat index 633RisingCat Wu, product lead for Claude Code, joins OpenAI9 sources
- Heat index 630NewSurgeOpenAI releases GPT-6 Cyber cybersecurity model7 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

