Summary (Overview)
- Core research question: Should looped transformers use truncated backpropagation through time (BPTT), and how should compute be allocated among forward loops, backward loops, model size, and training tokens?
- Key contribution: A unified scaling law with an effective parameter count that jointly models model size, training tokens, and independent forward/backward loop counts, fitted on nearly 600 training runs (58M–919M parameters).
- Main finding on truncation: When the forward-loop count is prescribed, truncation can be optimal (saving compute for larger models/more tokens); but when both loop counts are free, full BPTT is optimal at every model size and compute budget.
- Compute allocation: At fixed model size, optimal loop count grows as and token count as ; when model size is free, no looping is optimal, but two fully trained loops nearly match the compute-optimal non-looped model with 27–32% fewer non-embedding parameters.
- Practical result: A (2,2) looped model achieves lower validation loss than the compute-optimal non-looped model with ~27% fewer parameters and only 8% more training compute.
Introduction and Theoretical Foundation
Background and Motivation
Looped transformers reuse a shared block of layers to increase computational depth without increasing trainable parameters (Dehghani et al., 2019; Geiping et al., 2025). Training typically uses BPTT, which is often truncated to the last few loops to save compute and activation memory. However, truncation yields biased gradients that may weaken the benefits of looping.
The central question: How do model size, training tokens, and forward/backward loops jointly affect loss, and should we truncate backpropagation under a fixed training compute budget?
Key Gaps in Prior Work
Existing scaling studies have limitations:
- Schwethelm et al. (2026) compares full BPTT with truncation to half the loops, fitting separate scaling laws per recipe.
- Parcae (Prairie et al., 2026) varies backward-loop counts in small experiments but fixes them to half the forward-loop count in its scaling study.
- No prior work provides a unified law for choosing both loop counts across model sizes and token budgets.
Architecture: Prelude–Recurrent–Coda
The model computes hidden states via a prelude , a shared recurrent block applied over loops, and a coda :
Parameters split as , where counts prelude/coda (run once) and counts the recurrent block (reused every loop).
Truncated BPTT
A loop setting with runs loops forward but backpropagates only through the last loops. The state is detached. Full BPTT corresponds to ; a standard transformer is . A backward loop costs twice the FLOPs of a forward loop.
Baseline Scaling Law
The coupled scaling law of Videau et al. (2026) for non-looped models:
Methodology
Experimental Setup
- Architecture: Prelude–recurrent–coda, following Schwethelm et al. (2026).
- Model sizes: Five sizes from 58M to 919M non-embedding parameters (Table 2).
- Corpus: 100B-token FineWeb-Edu (Penedo et al., 2024).
- Optimizer: MuonH for transformer-block and input-injection matrices; AdamW for embeddings, output, and normalization parameters.
- Runs: 592 total, including a scaling suite of 347 configurations spanning 1.1–1,291 tokens per parameter and fifteen combinations with .
- Fitting: 230 configurations for fitting; 117 reserved for holdout tests.
Model Sizes
| Size | d | Layers | N | |
|---|---|---|---|---|
| 60M | 768 | 2/4/2 | 57.8M | 0.510 |
| 120M | 1024 | 2/5/2 | 115.4M | 0.564 |
| 240M | 1280 | 3/6/3 | 239.2M | 0.507 |
| 480M | 1664 | 3/7/4 | 470.8M | 0.506 |
| 1B | 2176 | 4/8/4 | 918.7M | 0.505 |
The Effective-Parameter Scaling Law
The law replaces with an effective parameter count:
Design Requirements for
The looping coefficient satisfies four requirements:
- Normalization: (single loop recovers non-looped model)
- Monotonicity: ,
- Zero-backward limit:
- Saturation: (finite ceiling )
Fitted Parameters
| E | A | H | α | β | κ | c | p | q |
|---|---|---|---|---|---|---|---|---|
| 0.29865 | 6.48695 | 7.63343 | 0.30568 | 0.39281 | 0.32510 | 1.11198 | 0.23677 | 1.02181 |
Fit and Prediction Errors ()
| Evaluation | Fits | RMSE | MAE |
|---|---|---|---|
| In-sample | 1 | 6.14 | 4.91 |
| One configuration out | 230 | 6.40 | 5.11 |
| One model size N out | 7 | 7.48 | 5.89 |
| One token budget D out | 11 | 6.42 | 5.12 |
| One (T, B) setting out | 15 | 8.67 | 6.74 |
Empirical Validation / Results
Key Finding 1: Loops Add Effective Parameters; Truncation Discounts Them
- Each fully trained loop adds effective parameters with diminishing returns toward a finite ceiling .
- Truncation discounts this gain.
- From the same setting, doubling adds more effective parameters than doubling (since : for ).
Key Finding 2: Truncation Helps at Prescribed Forward-Loop Count
When is prescribed, truncation can be optimal. The compute-equivalent size is:
The optimization reduces to minimizing :
| T | B* | N* | D* | ||
|---|---|---|---|---|---|
| 1 | 1 | 1.000 | 1.000 | 1 | 1 |
| 2 | 2 | 1.031 | 1.031 | 1 | 1 |
| 4 | 2 | 1.204 | 1.430 | 1.27 | 1.08 |
| 8 | 2 | 1.580 | 2.376 | 1.51 | 1.20 |
| 16 | 2 | 2.343 | 4.339 | 1.70 | 1.31 |
At , the law selects and predicts a 34% compute saving at equal optimized loss.
Key Finding 3: Full BPTT Is Optimal When Both Loop Counts Are Free
When both and can be chosen, the problem becomes:
The optimal split uses full BPTT whenever . With fitted values and , we have by a wide margin. Full BPTT is optimal at every compute.
Matched-compute experiments confirm: at , (4,4) achieves lower loss than (8,2) at every size:
| Size | () | () | ||
|---|---|---|---|---|
| 60M | 2.41 | 2.5211 | 2.4933 | 2.78 |
| 120M | 4.59 | 2.3843 | 2.3696 | 1.47 |
| 240M | 8.28 | 2.2778 | 2.2642 | 1.36 |
| 480M | 15.29 | 2.1845 | 2.1738 | 1.07 |
| 1B | 28.38 | 2.1144 | 2.1057 | 0.87 |
Key Finding 4: Fixed Model Size — Loops Grow Slowly
At fixed model size with full BPTT ():
With fitted values (, ):
A tenfold increase in compute raises the optimal loop count by ~1.7× and the token count by ~5.8×.
Key Finding 5: Free Model Size — No Looping Is Optimal
When model size is free, the law favors the non-looped model. The optimal allocation:
The reason: replacing a shared recurrent block with untied copies gives greater effective size since for . However, , so two shared loops provide nearly the effective size of two untied copies.
Key Finding 6: Two Fully Trained Loops Are Competitive
- At equal compute, (2,2) models stay within 0.008 nats of the non-looped model with 27–32% fewer non-embedding parameters.
- With 8% more compute, the (2,2) model's loss falls 0.007 nats below the compute-optimal non-looped model (Figure 15), while still having 27% fewer parameters.
Theoretical and Practical Implications
Theoretical Contributions
- Unified scaling law: First law jointly modeling forward and backward loop counts independently, using a bounded effective-parameter gain with just three loop coefficients ().
- Explanation of truncation's value: Resolves the apparent contradiction between prior results — truncation helps only when the forward-loop count is fixed; full BPTT wins when both counts are tunable.
- Compute allocation rules: Extends Parcae's fixed-size analysis beyond prescribed truncation, providing asymptotic exponents for loop/token allocation.
Practical Implications
- Parameter efficiency: Two fully trained loops offer a practical sweet spot — nearly matching non-looped compute-optimal models with 27–32% fewer parameters.
- Memory-constrained training: At fixed model size, practitioners should allocate most additional compute to tokens, growing the loop count only slowly ().
- Training recipe guidance: When both loop counts can be chosen, full BPTT is preferable to truncation despite its higher per-step cost.
Comparison with Prior Scaling Laws
| Study | Loop gain | BPTT | Regime |
|---|---|---|---|
| Schwethelm et al. (2026) | power law () | fixed depth | |
| Parcae (Prairie et al., 2026) | linear () | fixed N | |
| Chen et al. (2026b) | bounded exp. () | full () | free N, mem. |
| Ours | bounded () | fixed & free N |
Conclusion
Main Takeaways
- Truncation's value is conditional: It helps only when the forward-loop count is prescribed; with both loop counts free, full BPTT is optimal at every model size and compute budget.
- Effective parameters framework: Loops add effective parameters with diminishing returns toward a finite ceiling; truncation discounts this gain.
- Compute allocation: At fixed size, and ; with free size, no looping is optimal but (2,2) is the best looped setting.
Future Directions
- MoE architectures: Whether conclusions extend to looped mixture-of-experts models remains open.
- Downstream tasks: Only validation loss was measured; reasoning and task performance need study.
- Deeper loops: Experiments capped at ; the gain ceiling and later switches remain extrapolations.
- Parameter allocation: The ratio of prelude/coda to recurrent parameters was fixed; varying it could affect loop gains and optimal loop counts.
Related papers
- Where to Spend Test-Time Compute in Recursive Reasoning
Gated Answer Resampling, a tuning-free test-time method that resamples only the decoded answer state, boosts TRM accuracy from 85.9% to 99.4% on Sudoku and 68.8% to 85.6% on PPBench at minimal compute cost.
- Multi-Reward Hacking: From Aggregation-Induced Drift to Trust-Anchored Defense
Symmetric reward aggregation in LLM post-training provably causes multi-reward hacking, favoring auxiliary rewards over correctness, and Trust-Anchored Gating reverses this collapse.
- Compaction Laundering: Provenance Destruction in Context-Compacting Coding Agents
Compaction laundering lets attackers forge user instructions that survive context summarization in flattening coding harnesses, enabling code execution with 87-100% success.