Skip to main content
EvidenceAI ModelsVisualization detail

Effect of multi-token prediction on accepted length.

MTP speculative decoding: acceptance length

Takeaway: Shows where the speed/quality gains come from architecturally.

MTP ablation

Ablation on coding scenarios; +20% over baseline.

Takeaway: Shows where the speed/quality gains come from architecturally.

MTP ablation

Shows where the speed/quality gains come from architecturally.

Rendering the interactive chart…

Expand data table
Download CSV
MTP speculative decoding: acceptance length: data table
DimensionSeriesValueValue basisSource
BaselineAcc len4.56ActualZ.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)
+ IndexShare + KVShareAcc len5.1ActualZ.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)
+ Rejection SamplingAcc len5.29ActualZ.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)
+ End-to-end TV LossAcc len5.47ActualZ.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)

MTP speculative decoding: acceptance length: full data table

SOURCEZ.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)
VALUE BASISActual
LAST VERIFIEDSep 10, 2026
How this is calculated

Data table

Download CSV
MTP speculative decoding: acceptance length: mtp_ablation data table (GLM-5.2 Benchmarks)
StepSeriesAcc lenSourceValue basis
Baselinemtp_ablation4.56Z.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)Actual
+ IndexShare + KVSharemtp_ablation5.1Z.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)Actual
+ Rejection Samplingmtp_ablation5.29Z.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)Actual
+ End-to-end TV Lossmtp_ablation5.47Z.ai: GLM-5.2: Built for Long-Horizon Tasks (2026-06-16)Actual

Method

How this evidence was built

What it measures

Source-backed values for all six charts come from the Z.ai glm-5.2 launch post (2026-06-16): long-horizon coding (FrontierSWE, PostTrainBench, swe-Marathon), standard coding (Terminal-Bench 2.1, swe-bench Pro, NL2Repo, DeepSWE, ProgramBench), reasoning (hle, CritPt, aime, hmmt, gpqa-Diamond, IMOAnswerBench), agentic (mcp-Atlas, Tool-Decathlon), the glm-5.2 vs glm-5.1 generational leap, and the mtp acceptance-length ablation.

Key context

  • Every numeric point carries a source citation and a basis label naming the table row.
  • Scores are reproduced verbatim from the Full Benchmark Table; cells the vendor published as "-" (not reported) are omitted, never estimated.

Key numbers

  • FrontierSWE: glm-5.2 74.4 vs Opus 4.8 75.1 vs gpt-5.5 72.6 vs Gemini 39.6 vs glm-5.1 30.5 (zai-glm52).
  • Terminal-Bench 2.1: glm-5.2 81 vs Opus 4.8 85 vs gpt-5.5 84 vs Gemini 74 (zai-glm52).
  • Generational leap: swe-Marathon 13.0 (5.2) vs 1.0 (5.1) (zai-glm52).
  • Mtp ablation quantifies the multi-token-prediction contribution to accepted length (zai-glm52).

Caveats

Caveat: these are the model developer’s self-reported figures under their stated harnesses and prompts (see the post’s footnotes); some competitor hle/CritPt cells are full-set scores. They are comparison-as-published, not an independent eval. Architecture context (not charted): 1M-token context (up from 200K), IndexShare cuts per-token indexer FLOPs ~2.9× at 1M, mit-licensed open weights.

Caveat: Some competitor scores are marked full-set vs public-set, not always like-for-like.

Do not use this to

  • Independent verification: every figure is vendor self-reported (zai-glm52).
  • Real-world reliability, latency or cost (benchmark scores only).

Scope

June 2026

Sources

Last verified 10 Sept 2026

How relevant was this information?