arXiv:2611.05611v1 Announce Type: new Abstract: Speculative decoding (SD) speeds up large language model (LLM) serving, but its gain depends on the workload's \emph{shape}, such as batch size and context length, and on its \emph{content}. A model-based drafter proposes a short block on any content, while a model-free drafter such as n-gram lookup proposes long copies at almost no cost when the output repeats its input, as in code editing. Adaptive verification spends a batch-wide verification budget on the draft tokens most likely to be accepted, but it supports only one model-based drafter. Model-free drafters provide no per-token confidence, so they cannot take part in budget allocation, and deployments must either fix one drafter or split their GPUs between drafters. We present \sys, a framework that runs a model-based and a model-free drafter on every step and gives each request the better of their chains, within adaptive verification and entirely on the GPU, which keeps asynchronous scheduling intact. The key idea is a price per verified draft token: the goodput that slot would earn elsewhere in the batch. Once the model-free drafter's tokens carry calibrated acceptance estimates, fit once on general text, this price puts both drafters' chains on one scale. Instantiated with \dspark and an n-gram drafter in vLLM, \sys achieves 1.10--1.62\x the output throughput of \dspark on code editing at batch size~4 and 1.04--1.27\x at batch size~128, while staying at 0.97--1.01\x of it on chat at temperature~0. A single deployment can therefore serve both workloads.
Hybrid Spark: Adaptive Speculative Decoding That Lets the Content Choose the Drafter
A paper posted to arXiv (2611.05611v1) presents Hybrid Spark, a speculative decoding framework that runs a model-based drafter and a model-free n-gram drafter on every step and gives each request the better of their chains within adaptive verification, all on the GPU. Instantiated with DeepSpark and an n-gram drafter in vLLM, Hybrid Spark reaches 1.10–1.62x the output throughput of DeepSpark on code editing at batch size 4 and 1.04–1.27x at batch size 128, while staying at 0.97–1.01x of it on chat at temperature 0. The authors argue a single deployment can therefore serve both workloads, addressing the limitation that model-free drafters provide no per-token confidence and cannot participate in adaptive verification's budget allocation.
Run your AI side-project on zahid.host
EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.