GO TO A SECTION

↑ ↓ to navigate · Enter to openExplore all sections →
FDEInterviews logo
ICLR 2024

Think before you speak: Training Language Models With Pause Tokens

Append 10 or 50 copies of a learned <pause> token to the prompt and read the answer only after the last one. Trained this way from pretraining on, a 1B model's SQuAD score rose from 36.4 to 55.9.

Breakdown by FDE Interviews · 11 min read · Updated

About the original · 2023
AUTHORS
Goyal, Ji, Rawat, Menon, Kumar, Nagarajan
FROM
Carnegie Mellon University, Google Research
PUBLISHED
Oct 2023 · ICLR 2024
CITED BY
373Semantic Scholar · Nov 2026
IN THIS BREAKDOWN · 10 SECTIONS

You can read 20% of this breakdown.

01

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.

THE IDEA, VISUALLY
STANDARD VS PAUSE INFERENCE (FIGURE 1) standard 25 + 4 is 29 with pauses (M = 10 or 50) 25 + 4 is <p> <p> <p> 29 outputs ignored until the last <p> PAUSE PRETRAINING (SECTION 3.1) The kid <p> is <p> playing soccer ~10% of positions are pauses, inserted at random; no loss on predicting a pause. One new embedding: 1,024 parameters on a 1B model. Pauses must be in pretraining AND finetuning: finetuning-only gains were small or negative. With zero pauses at inference, the pause-trained model breaks; with as few as 2 it recovers. 1B MODEL, MEAN OF 5 RUNS (TABLE 1) SQuAD exact match 36.4 40.2 55.9 CommonSenseQA exact match 26.9 28.8 34.8 GSM8k accuracy 7.5 6.9 8.5 HellaSwag F1 37.8 37.9 37.8 bars start at 30, 20, 0 and 30 respectively standard pauses in finetuning pauses in both Pauses won on 8 of 9 tasks. SQuAD: +19.5 points by Table 1 (the text says 18%). GSM8k: +1.0 on 7.5. arXiv 2310.02226, CMU and Google Research, ICLR 2024
Pause inference appends 10 or 50 copies of one learned <pause> token to the prompt and reads the answer only after the last, so every layer has more positions to compute with before the answer. During pretraining, pauses are inserted at random positions and never predicted. With pauses in both pretraining and finetuning, the 1B model gained on 8 of 9 tasks, most on SQuAD; with pauses only in finetuning, gains were small or negative.
Research notes: the problem, approach and results
36.4 → 55.9

SQuAD exact match for the 1B model, standard training vs pauses in pretraining and finetuning (Table 1)

8 of 9

downstream tasks where pause pretraining plus pause finetuning beat standard training (Table 1)

1,024

new parameters: one <pause> embedding on a 1B model (Section 4.1)

THE PROBLEM

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.

THE IDEA

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.

THE RESULT

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.

02

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.

THE FULL BREAKDOWN

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

Get Premium · ₹2,000 / $25
  • ◇1 architecture diagram
  • </>1 runnable code experiment
  • ▦2 results tables
  • ?5 interview questions with answers
  1. 03Key takeaways

    What pauses add, where they help, the conditions, the ablations and two misreadings

    Free account
  2. 04How it works

    Pretraining, finetuning and inference with pauses, the setup, and the width argument

    Premium
  3. 05The numbers that matter

    Table 1 across nine tasks, the finetuning-only and pretraining-only controls, and the ablations

    Premium
  4. 06Try it yourself

    Recheck the headlines, measure gains in standard errors, bound the selection effect and count costs

    Premium
  5. 07Where it breaks

    Pretraining required, task-specific counts, zero-pause collapse, small models and slips

    Premium
  6. 08Using it on a deployment

    Judging "thinking room" claims, model templates, and when width-style compute is worth it

    Premium
  7. 09Interview angles

    Five questions this paper prepares you for, with answer hints

    Premium
Back to the paper library →