IN THIS BREAKDOWN · 10 SECTIONS
You can read 20% of this breakdown.
The paper in one minute
To produce its next token, a decoder-only transformer computes one vector per preceding token in every layer. If the prompt has K tokens, each layer gets K positions of computation before the answer, no more. The authors ask what happens if the model may compute over K + M positions, by appending M dummy tokens and waiting to read the answer until the last one.
They use one new learned token, <pause>, outside the normal vocabulary. In pretraining, they insert pauses at random positions, about 10% of each 2,048-token sequence, and never ask the model to predict a pause. In finetuning and at inference, they append 10 or 50 pauses to the prompt and ignore the model's outputs until the last pause, then read the answer. The only new parameters are the pause embedding's 1,024 numbers.
With a 1B-parameter model pretrained on 200B tokens of C4, pauses in both pretraining and finetuning beat standard training on 8 of 9 downstream tasks. SQuAD exact match rose from 36.4 to 55.9, CommonSenseQA from 26.9 to 34.8, and GSM8k from 7.5% to 8.5%. Two conditions mattered. Adding pauses only at finetuning, to a normally pretrained model, gave small and inconsistent gains and sometimes hurt. And the pause-trained model needs its pauses: with zero pauses at inference its performance collapsed, though as few as two brought it back.
Research notes: the problem, approach and results
SQuAD exact match for the 1B model, standard training vs pauses in pretraining and finetuning (Table 1)
downstream tasks where pause pretraining plus pause finetuning beat standard training (Table 1)
new parameters: one <pause> embedding on a 1B model (Section 4.1)
A transformer computes the next token from exactly as many positions as it has seen, so the amount of computation per layer before an answer is tied to the prompt's length. Earlier attempts to add dummy tokens at inference, such as dots, did not help off-the-shelf models.
Add a learned <pause> token. In pretraining, insert it at random positions and skip the loss for predicting it. In finetuning and inference, append a fixed number of pauses to the prompt and start reading the answer only after the last one.
For a 1B model pretrained on 200B tokens of C4, pauses in both pretraining and finetuning beat standard training on 8 of 9 tasks: SQuAD exact match 36.4 to 55.9, CommonSenseQA 26.9 to 34.8, GSM8k 7.5 to 8.5. Pauses added only at finetuning gave mixed results, and removing pauses at inference broke the pause-trained model.
Why it matters to an FDE
Pause tokens are a training technique, not something you can add to a hosted model, but the paper settles a question that comes up in prompt engineering and explains why some tricks do not work.
Padding a prompt with dots does not buy computation. The authors confirm that appending periods to a normally trained model gave no gains, as earlier work found. Extra positions help only when a model has been trained to use them. If someone proposes "give the model room to think" by padding prompts, the evidence says it will not help an off-the-shelf model.
Computation can come from width as well as length. Chain of thought adds sequential steps. Pauses add parallel positions per layer without adding output text, which suits tasks like reading comprehension where the model must look in many places at once. The SQuAD gain, far larger than GSM8k's, fits that.
Training choices show up at inference. A model trained with pauses may depend on them; this one failed without any. When a vendor's model uses special tokens or formats learned in training, deviating from them at inference can be costly, so the serving template is part of the model.
Understand the mechanism. Try it on a real problem.
Unlock this breakdown and 290 more papers.
Premium opens every paper in full, plus every answer, concept, course and guide on the site. One payment for six months of access.
6 months · One payment · No auto-renewal
- ◇1 architecture diagram
- </>1 runnable code experiment
- ▦2 results tables
- ?5 interview questions with answers
- 03Key takeaways
What pauses add, where they help, the conditions, the ablations and two misreadings
Free account - 04How it works
Pretraining, finetuning and inference with pauses, the setup, and the width argument
Premium - 05The numbers that matter
Table 1 across nine tasks, the finetuning-only and pretraining-only controls, and the ablations
Premium - 06Try it yourself
Recheck the headlines, measure gains in standard errors, bound the selection effect and count costs
Premium - 07Where it breaks
Pretraining required, task-specific counts, zero-pause collapse, small models and slips
Premium - 08Using it on a deployment
Judging "thinking room" claims, model templates, and when width-style compute is worth it
Premium - 09Interview angles
Five questions this paper prepares you for, with answer hints
Premium - 10Read next
Where to go from here on this site
Premium
