LatentLoop: Scaling Looped MoE Models with Asymmetric Compute Allocation
Zefeng He, Yunkai Chai, Xiaoyang Chen, Tong Zhu, Zongliang Wu, Yun Luo, Yafu Li, Yu Cheng
SJTU · Shanghai AI Lab · USTC · CUHK · NTU
Published October 14, 2026 · on the feed October 15, 2026 · ▲ 67 · arXiv 2610.19975
The abstract
Looped Mixture-of-Experts (MoE) models combine parameter reuse with sparse computation to improve performance under matched budgets. Prior work demonstrates that different loop visits can play different roles even when they share parameters. To probe the contributions of different loop visits, we learn separate residual coefficients in a model that applies a shared block twice, observing a smaller scale in the first visit. Fixed coefficient experiments show that reducing the first visit's scale preserves or improves performance, whereas the same reductions to the second hurt it. This asymmetry motivates us to explore asymmetric compute allocation. We propose LatentLoop, which compresses the first visit's sequence, retains full resolution in the second, and reallocates saved computation to increase the hidden size. We further learn how strongly the first visit updates the full sequence, and share MoE weights across visits while using separate attention parameters to accommodate their different sequence resolutions. Across 15 configurations spanning 1.3B--7B parameters, with the largest budget exceeding 10^{21} FLOPs, LatentLoop consistently lowers validation NLL. At a fitted NLL of 1.988, predicted compute savings are 19.0\% and 7.9\% relative to vanilla MoE and the looped baseline. It also improves average scores on nine benchmarks at all sizes in 0-shot and 5-shot settings. These results suggest asymmetric compute allocation is a promising direction for looped MoE models.
The Brief
2:42A short podcast summary of the paper. Written and voiced by AI.
Transcript
LatentLoop. Scaling Looped MoE Models with Asymmetric Compute Allocation. By Zefeng He and seven others, from Shanghai Jiao Tong University, the Shanghai AI Lab, and three other institutions. Published on the fourteenth of October. Its code repository is public and real: thirteen source files.
Looped Mixture-of-Experts models pass the input through the same block more than once, combining parameter reuse with sparse computation to do better under matched budgets. Earlier work has shown that different visits to the loop can play different roles, even though they share parameters. If the visits do different jobs, then spending the same compute on each of them may not be the best use of the budget. The question is which visit deserves what.
To probe that, the authors take a model that applies a shared block twice and learn a separate residual coefficient for each visit. The first visit ends up with a smaller scale. Fixing the coefficients by hand sharpens the picture: reducing the first visit's scale preserves or even improves performance, while the same reductions applied to the second visit hurt it. That asymmetry motivates asymmetric compute allocation, and LatentLoop is the resulting design.
LatentLoop compresses the sequence during the first visit, keeps full resolution during the second, and reallocates the computation saved to increase the hidden size. On top of that, the model learns how strongly the first visit updates the full sequence. The MoE weights are shared across visits, while each visit gets its own attention parameters, to accommodate the different sequence resolutions the two visits work at.
Put together, the first pass is cheaper and coarser, working over a compressed sequence, and how much it changes the full sequence is itself learned rather than fixed. The second pass sees everything at full resolution. The compute that the compression frees is not simply banked as savings. It is spent again, on a wider model.
The evaluation spans fifteen configurations, from one point three billion to seven billion parameters, with the largest budget exceeding ten to the power twenty-one FLOPs. Across all of them, at small scale and large, LatentLoop consistently lowers validation NLL.
At a fitted NLL of one point nine eight eight, the predicted compute savings are nineteen point zero percent relative to vanilla MoE, and seven point nine percent relative to the looped baseline. LatentLoop also improves average scores on nine benchmarks at every size, in both zero-shot and five-shot settings.
The authors frame asymmetric compute allocation as a promising direction for looped MoE models. The path to it is the part to hold onto: a learned coefficient hinted that the first visit mattered less at full strength, a controlled reduction confirmed it, and the design follows directly. Spend less on the visit that needs less, and give the savings to width.
Paper Quest · 7 chapters · about 40 min
Play this paper
Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.
Chapter 1 🧩 · The problem
Two passes, equal cost, unequal value. Something here is waste.
You build language models that run their middle layers twice with the same weights, using sparse experts, and compare them fairly against rivals with equal parameters, cache and compute.
The road ahead
- 1 · The problem ~7 min A looped model spends equal compute on two passes through the same layers, even though one pass seems to matter far less than the other.
- 2 · What came before ~3 min
- 3 · The key idea ~8 min Since the first pass wants small updates, run it on a shorter, compressed sequence, and spend the saved compute on a wider model.
- 4 · Choose your own research ~3 min
- 5 · Build the method ~8 min Compress the sequence for the first visit, write its update back with a learned strength, then run the second visit at full resolution.
- 6 · The experiment ~6 min You’ll guess: In a model applying a shared block twice, shrinking which visit's residual scale preserved or improved performance?
- 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Free, with Google or an email address. Your stars and progress are kept.