Repeated-data pretraining favors smaller batches, finds Sewon Min's GPU-time tradeoff study
sewon__min · x · 2026-11-04
Sewon Min (UC Berkeley & AI2) released Scaling Repeated-Data Pretraining, studying how to pretrain when compute is abundant but unique data is finite.
- Batch size must be retuned: validation loss vs. batch size is U-shaped; small-batch gradient noise acts as implicit regularization, so optimal batches are smaller than usual. Batch tuning extends beneficial epochs from 8→20 for a 1.5B model and 40→112 for 153M.
- Recipes can adapt to repetition: repacking documents each epoch, weight tying, and positive embedding weight decay all help, pushing best checkpoints to epoch 32/240.
- GPUs and time are separate resources: tight deadlines favor larger batches, yet under a fixed budget a smaller batch with fewer GPUs can beat a larger batch with more GPUs—challenging the habit of maximizing data parallelism under deadlines.
Takeaway: when unique data becomes the binding constraint, both training recipes and compute allocation must change. rosinality notes small-batch wisdom from old deep learning may be coming back.
More from Infra
- Analyst: DeepSeek has post-trained V4 on Ascend since summer; real question is scaling to 5T+ params — AccBalanced · 2026-11-04
- Reddit user seeks uncensored local model that runs on a weak PC for search and bulk downloads — Emotional_Orange_279 · 2026-11-04
- NIDO ships fully offline Android AI assistant with encrypted memory and post-quantum messaging — NIDO_007 · 2026-11-04
- Fireworks Forge keynote: Sovereign stack, Ember next-gen targeting 30x efficiency, No-GPU — AccBalanced · 2026-11-04
- Dylan Patel: CoreWeave sold out for 6 months, Nebius demands full-year prepay — AccBalanced · 2026-11-04
- AMD and Arista beat expectations as AI infrastructure engines keep humming — TiernanRayTech · 2026-11-04