Throughput improvement is the increase in tokens generated per second achieved by speculative decoding, often measured in a batched inference setting. It is the core engineering objective of the technique, directly translating to lower compute cost per token and higher system capacity. The improvement is a function of the acceptance rate and the verification cost, where a high rate of accepted draft tokens and efficient parallel verification yield the greatest gains.
Glossary
Throughput Improvement

What is Throughput Improvement?
Throughput improvement is the primary performance metric for speculative decoding, quantifying the increase in tokens generated per second compared to standard autoregressive inference.
This metric is distinct from latency reduction, as it measures aggregate system output under load rather than the time for a single request. In production, throughput is maximized by optimizing the small-big model pair, tuning the speculative factor, and implementing batch verification to fully saturate GPU hardware. The ultimate speedup factor demonstrates the technique's value for scaling high-volume inference workloads cost-effectively.
Key Metrics for Measuring Throughput
Throughput improvement in speculative decoding is quantified by several key performance indicators that measure the efficiency of the draft-target model interaction and its impact on token generation speed.
Acceptance Rate
The acceptance rate is the percentage of tokens proposed by the draft model that are accepted by the target model during the verification forward pass. It is the primary determinant of speculative decoding's success.
- Calculation: (Number of accepted draft tokens / Total draft tokens proposed) * 100%
- Impact: A higher acceptance rate directly increases the speedup factor by reducing the frequency of costly rollbacks to autoregressive generation.
- Typical Range: Effective speculative decoding systems often achieve acceptance rates between 70-85% for well-aligned small-big model pairs.
Speedup Factor
The speedup factor is the ratio of the time taken for standard autoregressive decoding to the time taken for speculative decoding, providing a direct measure of latency reduction.
- Formula: Speedup = T_autoregressive / T_speculative
- Dependencies: It is a function of the acceptance rate, the speculative factor (γ), and the relative computational costs of the draft and target models.
- Theoretical Maximum: With a perfect draft model, the speedup is bounded by γ + 1. In practice, speedups of 2x-3x are common for large language models like Llama 2 70B.
Tokens Per Second
Tokens per second (TPS) is the absolute throughput metric, measuring the total number of tokens generated by the system per unit time. This is the ultimate business metric for inference cost.
- Measurement: Should be measured in a batched inference setting under realistic load to account for system overhead.
- Components: TPS is influenced by the speedup factor, the target model's native latency, and the efficiency of the batch verification process.
- Use Case: This is the key metric for CTOs and engineering managers calculating inference cost optimization and infrastructure scaling requirements.
Verification Efficiency
Verification efficiency measures the computational cost of the target model's parallel verification pass relative to the cost of generating the same number of tokens autoregressively.
- Core Principle: For a net speedup, the cost of verifying γ tokens must be less than the cost of generating γ tokens autoregressively.
- Factors: Efficiency is determined by the implementation of tree attention, speculative KV cache reuse, and operator/kernel fusion in the verification step.
- Optimization: High verification efficiency minimizes the verification cost, making speculative decoding viable even with moderate acceptance rates.
Effective Batch Utilization
Effective batch utilization quantifies how well the system uses parallel compute resources (e.g., GPUs) during the batch verification of candidate sequences from multiple requests.
- Importance: Speculative decoding's throughput gains are maximized in a model serving context with continuous, dynamic request batching.
- Metric: It measures the ratio of active computational units during the verification forward pass versus idle time.
- Relationship: High utilization is enabled by continuous batching systems that can dynamically group requests with varying speculative factors and sequence lengths.
Rollback Frequency
Rollback frequency measures how often the speculative process fails and must revert to standard autoregressive generation from the target model, triggered by a token rejection.
- Inverse Metric: It is directly related to the acceptance rate. A low acceptance rate leads to high rollback frequency.
- Cost: Each rollback incurs a penalty, as the work to draft the rejected token sequence is wasted, and generation continues at the slower autoregressive pace.
- Mitigation: Techniques like confidence thresholding and dynamic draft selection aim to reduce rollback frequency by making the draft model more conservative.
How Throughput Improvement is Achieved
Throughput improvement in speculative decoding is the direct result of replacing multiple sequential autoregressive steps with a single, parallel verification step.
Throughput improvement is achieved by amortizing the high latency of a single forward pass of the large target model across multiple predicted tokens. Instead of generating one token per pass, a fast draft model proposes a candidate sequence of tokens (e.g., 3-5 tokens). The target model then verifies this entire sequence in one parallelized forward pass, using a tree attention or batched scoring mechanism. If most draft tokens are accepted, the effective tokens generated per second (throughput) increases proportionally.
The speedup is mathematically bounded by the acceptance rate and the verification cost. For a net gain, the time saved by skipping autoregressive steps must exceed the overhead of running the draft model and the batched verification. This is optimized by tuning the speculative factor (length of the candidate sequence) and employing hardware-aware speculation to maximize GPU utilization through batch verification across multiple requests, transforming latency reduction into scalable throughput gains.
Throughput vs. Latency: A Critical Tradeoff
This table compares the primary performance characteristics and optimization goals of throughput and latency, which are inversely related in most inference systems. Understanding this tradeoff is essential for selecting the correct speculative decoding parameters and hardware configuration.
| Metric / Characteristic | Throughput (Tokens/Second) | Latency (Time-to-First-Token) |
|---|---|---|
Primary Goal | Maximize total work completed per unit time | Minimize the delay for a single request to start producing output |
Optimization Focus | GPU utilization, batch size, continuous batching | Single request execution path, model size, speculative decoding speedup |
Key Measurement | Tokens generated per second across a batch (e.g., 10,000 tok/sec) | Milliseconds from request receipt to first token emission (e.g., 50 ms) |
Scaling Behavior | Improves with larger batch sizes (amortizes fixed costs) | Degrades with larger batch sizes (increased queueing and compute time) |
Typical Use Case | Offline processing, bulk text generation, model pre-filling | Interactive chat, real-time APIs, user-facing applications |
Hardware Leverage | Maximizes parallel compute (Tensor Cores, high occupancy) | Minimizes serial dependencies (fast memory, high clock speeds) |
Impact of Speculative Decoding | Major increase via parallel verification of candidate sequences | Potential reduction, dependent on draft model speed and acceptance rate |
Primary Bottleneck | Memory bandwidth for weight loading (memory-bound) | Serial autoregressive steps (compute-bound for small batches) |
Frequently Asked Questions
Throughput improvement is a primary metric for evaluating speculative decoding, measuring the increase in tokens generated per second. These questions address the core mechanisms and trade-offs involved in achieving this speedup.
Throughput improvement is the increase in tokens generated per second (tokens/sec) achieved by speculative decoding compared to standard autoregressive inference. It quantifies the efficiency gain from using a small, fast draft model to propose a candidate sequence of tokens, which are then verified in parallel by the larger target model in a single verification forward pass. The improvement is calculated as the ratio of speculative decoding throughput to baseline autoregressive throughput. Key factors influencing throughput include the acceptance rate of draft tokens, the speculative factor (gamma), the relative speeds of the draft and target models, and the verification cost of the parallel scoring step. In batched inference settings, throughput improvement is the critical business metric, as it directly translates to lower compute cost per token and higher system capacity.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Throughput improvement in speculative decoding is the increase in tokens generated per second, primarily achieved by verifying multiple draft tokens in a single forward pass of the target model. The following concepts are critical for understanding and optimizing this metric.
Parallel Decoding
The core mechanism enabling throughput gains. Instead of generating one token at a time (autoregressively), the target model verifies a sequence of candidate tokens in a single, batched forward pass. This amortizes the fixed cost of loading the model's weights and attention states over multiple tokens.
- Key Benefit: Reduces the number of serial model executions.
- Implementation: Requires batching the candidate sequence and using a modified attention mask to allow the target model to score all positions simultaneously.
Acceptance Rate
The percentage of tokens proposed by the draft model that are accepted by the target model. This is the primary determinant of effective throughput improvement.
- High Acceptance Rate (>80%): Means most draft tokens are correct, leading to a near-ideal speedup proportional to the speculative factor.
- Low Acceptance Rate: Causes frequent rollbacks, wasting the compute spent on drafting and verification. The net speedup is calculated as
Speedup = 1 / ( (1/γ) + (1 - α) ), whereγis the speculative factor andαis the acceptance rate.
Speedup Factor
The quantitative measure of throughput improvement. It's the ratio of wall-clock time for standard autoregressive decoding to the time for speculative decoding.
- Theoretical Maximum: Bounded by the speculative factor (γ). If every draft token is accepted, the speedup approaches
γ. - Real-World Range: Typically between 1.5x and 3.5x for well-tuned small-big model pairs, as it must offset the verification cost of the target model's parallel forward pass.
- Measurement: Must be measured in a batched inference setting under realistic loads to account for system overhead.
Verification Cost
The computational overhead incurred when the target model scores the candidate sequence. This cost must be less than the time saved by not generating those tokens autoregressively for a net speedup.
- Components: Includes the FLOPs for the extra forward pass and the memory bandwidth cost of handling the speculative KV cache.
- Optimization: Techniques like early stopping (halting verification upon first rejection) and efficient batch verification across multiple requests are used to minimize this cost.
Batch Verification
The process of verifying candidate sequences from multiple independent requests or beams in a single forward pass of the target model. This is essential for achieving high aggregate throughput in a production serving system.
- System-Level Throughput: Maximizes GPU utilization by maintaining a high batch size, even when individual requests are at different stages of the speculative decoding loop.
- Challenge: Requires sophisticated scheduling to align the drafting and verification phases across heterogeneous requests without introducing excessive latency.
Hardware-Aware Speculation
Tuning speculative decoding parameters based on the underlying hardware's characteristics to maximize throughput.
- Key Parameters: The speculative factor (γ) is often chosen based on memory bandwidth constraints and the target model's parallel compute efficiency.
- Memory Bound vs. Compute Bound: On memory-bound systems, a larger γ may not yield gains due to KV cache overhead. On compute-bound systems, a larger γ can better utilize parallel cores.
- Goal: To find the optimal operating point on the latency-throughput tradeoff curve for a specific deployment hardware (e.g., specific GPU architecture).

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us