The Art of Efficient Reasoning: Data, Reward, and Optimization — A Deep Analysis
> Paper: The Art of Efficient Reasoning: Data, Reward, and Optimization > arXiv: 2602.20945 | v3, 2026-03-20 > Authors: Taiqiang Wu, Zenan Xu, Bo Zhou, Ngai Wong (University of Hong Kong + Tencent) > Experiment scale: ~200K GPU hours > Validated models: Qwen3 series (0.6B → 30B)
One-Sentence Takeaway
The paper shows, with ~200K GPU hours, that teaching a model to "think short" is harder than teaching it to "think correctly" — and that training data selection matters more than reward function design.
Why Long CoT Is a Problem
Chain-of-Thought reasoning makes LLMs smarter (see Qwen3, DeepSeek-R1), but:
- High latency: users can't wait for 30k-token thought processes
- High cost: inference-time token consumption costs real money
- Overthinking: models fall into pointless self-repetition
- Easy: ≥4 correct out of 8 rollouts
- Hard: ≤4 correct out of 8
- N=8 → 24: faster length adaptation, more stable refinement
- N=24 → 32: narrow gains, especially on hard tasks
- Code tasks (LCB): almost no benefit
- Paper: arXiv 2602.20945
- Project page: https://wutaiqiang.github.io/project/Art
- Related survey: Efficient Reasoning Models: A Survey
Prior work focused almost exclusively on reward shaping while ignoring a more fundamental question: how should training data be selected, and how should optimization be done?
A Two-Stage Paradigm: Length Adaptation → Reasoning Refinement
Stage I: Length Adaptation
In the first 200–400 steps, the model learns to "survive." With rewards zeroed beyond ~4k tokens, average length collapses exponentially from ~6k to ~2k, and policy entropy drops sharply. The dominant signal is constraint satisfaction, not reasoning quality.
Stage II: Reasoning Refinement
Once length plateaus, real learning begins: performance (Mean@8) keeps climbing while entropy rises again as the model explores how to pack more useful information into a limited budget. The dominant signal becomes logical optimization.
Key insight: the two stages optimize different objectives — survival, then evolution. Monitoring only final performance hides the sharp phase transition visible in the length distribution.
Counter-Intuitive Finding: Easy Prompts Beat Hard Prompts
The authors split the DeepScaleR dataset by pass rate:
| Training data | Stability | Downstream performance | |---|---|---| | Hard | Catastrophic failure | Entropy explosion, length collapse | | Easy | Stable convergence | Matches or beats full dataset | | Full | Moderate | Baseline |
Why: positive reward density. On hard data, negative samples dominate the RL signal, so the model learns "how to end quickly to avoid penalties" instead of "how to reason correctly." On easy data, frequent correct answers teach the model what correct short answers look like, which then transfers to harder tasks. This overturns the classic curriculum-learning intuition — build stable length control on easy data first, then generalize.
Negative-Sample Handling: Three Failure Modes
How you penalize wrong answers matters as much as how you reward right ones:
1. "Short = correct" trap (-I, -L&C-S&I): when only short-correct gets rewarded, the model hacks the bias — entropy explodes after ~400 steps and reasoning is abandoned. 2. Short-only trajectories (-L&C-L&I): masking all overlong traces lets the model probe the boundary, producing long, mostly wrong outputs. 3. Best policy (-L&C): don't penalize overlong *correct* answers; penalize only errors. Slightly longer outputs, best performance.
The simplest win: set the rollout limit equal to the target length (\(L_R = L_T = 4k\)). This minimizes the length gap between positive and negative samples and avoids the explicit "short = correct" bias.
Rollout Count N: Diminishing Returns
Larger N acts mainly as a variance reducer, not a capability expander: Mean@8 improves clearly, Pass@8 barely.
Budget Sensitivity: Same Strategy, Different Fates
| Budget | Kimi strategy | Truncation | Laser | |---|---|---|---| | 2k | Best | Moderate | Poor | | 32k | Reasoning collapse | Stable | U-shaped recovery |
No free lunch: any efficient-reasoning strategy is budget-dependent; single-point evaluation gives misleading conclusions.
Cross-Domain Generalization: Math → Code
On LiveCodeBench, length biases learned on math prompts transfer to code, and strategy rankings are preserved. Efficient reasoning is a transferable meta-skill — how to organize thought within a length budget.
Qwen3 Full-Series Results
| Model | Baseline Mean@8 | Optimized Mean@8 | Length compression | |---|---|---|---| | Qwen3-0.6B | 13.33 | 24.58 | 14.9k → 8.9k (-40%) | | Qwen3-1.7B | 35.00 | 38.75 | 17.7k → 11.2k (-37%) | | Qwen3-4B-Instruct | 45.42 | 46.67 | 9.1k → 4.8k (-47%) | | Qwen3-4B-Thinking | 75.83 | 76.25 | 20.9k → 16.0k (-23%) | | Qwen3-8B | 65.83 | 67.08 | 17.9k → 12.8k (-28%) | | Qwen3-30B-A3B-Instruct | 60.83 | 60.83 | 6.9k → 5.1k (-26%) | | Qwen3-30B-A3B-Thinking | 84.17 | 86.25 | 17.3k → 14.8k (-15%) |
Trends: smaller models benefit most (0.6B's Mean@8 doubled); Thinking models have less room to compress; Instruct models reach the best compression ratio at 4B (-47%).
Independent Commentary
1. Easy-first data: industry teams intuitively train on hard data; this drowns the RL signal in negatives. Build a stable short-thinking baseline on easy data first. 2. Engineering the two stages: explicitly freezing parameters for length control, then unfreezing for reasoning refinement, is a natural extension the paper doesn't explore. 3. Reward hacking: if "short" and "correct" can be optimized separately, the model picks the easier one — reward design must prevent decoupling. 4. Multi-budget evaluation (2k/8k/32k at minimum) should become a standard practice. 5. Generalization limits: only math → code was tested; whether length control generalizes across more diverse domains is open.
Actionable Advice for Practitioners
1. Data selection > reward design: ensure enough "short and correct" samples before tuning rewards 2. Align rollout limit with target length: \(L_R = L_T\) is the simplest effective setting 3. Monitor length distributions, not just averages — check distributions conditioned on correctness 4. Multi-budget evaluation is mandatory: test at least 2k, 8k, 32k 5. N=24 is the sweet spot; beyond 32, gains are limited 6. Thinking models still need compression: 15–25% length savings remain available