Tencent published tencent/Qwen3.8-27B-DSpine-b16 on Hugging Face at 14:20 UTC on 2026-11-07: a five-layer speculative-decoding draft model of about 2B parameters with block size 16 and an 8,192-token sliding window, under Apache 2.0, with code at GitHub Tencent/DSpine and the paper at arXiv 2609.36173. The model card (vendor figures) shows that with SGLang 0.5.22, BF16 and concurrency 8, output throughput on a SWE-bench Pro replay at xhigh reasoning rose from about 248 to about 791 tokens/s (about 3.19x), versus 2.87x for the official DFlash2; acceptance length beat DFlash2 in all 10 agent settings. Note that DSpine drafts 16 tokens per block while DFlash2 drafts 8, so the setups are not identical, and no third-party reproduction exists yet.
Key Takeaways
- ✓Release: Tencent uploaded tencent/Qwen3.8-27B-DSpine-b16 at 14:20 UTC on 2026-11-07; about 2.03B parameters (about 4GB in BF16), five layers, block size 16, 8,192-token sliding window, Apache 2.0
- ✓Throughput (vendor figures): SWE-bench Pro replay at xhigh reasoning went from about 248 to about 791 tokens/s, about 3.19x; DFlash2 reached 2.87x
- ✓Best speedup (vendor figures): about 3.84x on WorkBuddy Office at low reasoning (DFlash2: 3.17x)
- ✓Acceptance length (vendor figures): 4.77 vs 4.00 for DFlash2 on SWE-bench Pro at xhigh; 7.20 vs 5.69 on GSM8K with greedy decoding
- ✓Caveat: DSpine drafts 16 tokens per block and DFlash2 drafts 8, so conditions are not identical; only model-card numbers exist so far, with no third-party reproduction

Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Core Background & Industry Pain Points
LLMs decode one token at a time and run the whole network for every token. For coding agents, with long outputs and many tool-call turns, that directly sets latency and how many requests each GPU can serve. Speculative decoding has a small draft model guess several tokens at once, then lets the large model verify them in one pass and keep the correct ones, without changing the output distribution. At 14:20 UTC on November 7, Tencent published tencent/Qwen3.8-27B-DSpine-b16 on Hugging Face, a draft model built specifically for Alibaba's open Qwen3.8-27B. Local-inference user Lasse (@lasse_ai) shared it on X saying it beats DFlash2 in every category; the post had about 148 likes and 120 bookmarks at capture.
Architecture Highlights & Underlying Mechanisms
According to the model card, DSpine generates draft tokens in parallel: each layer passes predicted predecessor features to adjacent positions, carrying causal dependencies through network depth instead of stepping forward one token at a time like an autoregressive drafter. This checkpoint is a five-layer draft model with about 2.03B parameters, block size 16 and an 8,192-token sliding window. Inference uses dynamic verification that references DSpark, with ReplaySSM enabled. Code is on GitHub at Tencent/DSpine, and the paper, "Draft in Parallel, Condition Through Depth", is arXiv 2609.36173. Tencent had already released a Qwen3-8B version in October.
Benchmarks & Measured Results
All figures below are vendor figures, measured with SGLang 0.5.22, BF16, FlashAttention 3 and concurrency 8. On a SWE-bench Pro replay at xhigh reasoning, autoregressive decoding ran at about 248 tokens/s, DFlash2 at about 712 (2.87x) and DSpine at about 791 (3.19x); on WorkBuddy Office at low reasoning DSpine reached 3.84x. Acceptance length was 4.77 vs 4.00 on SWE-bench Pro at xhigh and 7.20 vs 5.69 on GSM8K with greedy decoding. Note that DSpine drafts 16 tokens per block while the official DFlash2 drafts 8, so the setups are not equivalent; each agent subset replays only 20 conversations, and there is no third-party reproduction yet.
Developer Hands-on Guide
Teams already running Qwen3.8-27B coding agents locally or on their own clusters can try it directly: clone Tencent/DSpine and run pip install -e ., then start sglang serve with --speculative-algorithm DSPINE and --speculative-num-draft-tokens 16 pointing at the draft model path; the model card lists the full flags, including ReplaySSM and Mamba cache options. The draft model adds about 4GB of VRAM. Speculative decoding does not change outputs, but the real speedup depends on your prompt mix and concurrency, so replay your own agent logs and compare before replacing DFlash2 or EAGLE-style drafters.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.