テクニカルガイド
Critical Batch Size
Critical batch size describes a transition in training efficiency: beyond it, larger batches give diminishing reductions in the number of updates needed to reach a target.
このページでは3 分で読めます
概要
It is a property of a training problem and performance target, not simply the largest batch that fits in accelerator memory. Choosing a batch also requires measuring elapsed time, total processed examples, and final task performance.
ディープダイブ
A batch is the set of training examples used to form an update. Increasing its size averages over more examples and can reduce gradient noise. With enough parallel hardware, a larger batch may also reduce how many sequential updates are needed to achieve a chosen performance level. But those improvements do not continue proportionally forever. Critical batch size marks a characteristic transition in this tradeoff. In the empirical model of McCandlish and colleagues, batches well below the critical scale are relatively efficient per example. Far above it, adding examples to each update brings diminishing reductions in the number of updates. This is a smooth change in efficiency, not a universal hard limit beyond which training cannot work. The research connects the transition to gradient noise scale and finds that it can shift as training progresses. Define a common target before comparing runs. For an invented example, batch 256 reaches that target in 4,000 updates, processing 1,024,000 examples. Batch 512 takes 2,200 updates but processes 1,126,400 examples. It saves 45% of the updates while using 10% more examples. That could be an attractive elapsed-time tradeoff, but only measured update times reveal the runtime benefit. These two observations alone do not identify a precise critical batch size. Sweep several global batch sizes and tune relevant optimizer settings fairly. Record examples or tokens, updates, elapsed time, and validation performance at the same target. Keep track of whether a learning-rate schedule is expressed in updates or processed data, since changing the batch changes that relationship. Memory capacity, communication, and kernel efficiency impose additional practical limits that the statistical concept alone does not describe.
戦略的影響
費用と予算
アーキテクチャの決定により、パフォーマンスと運用コストが何年にもわたって推進されます。
より明確な判決
技術教育は、チームが最新のスタックだけでなく、適切なスタックを選択するのに役立ちます。
品質管理
より良いエンジニアリングの選択により、本番環境での信頼性に関するインシデントが減少します。
The Future of Critical Batch Size
Adaptive batch schedules may become easier to evaluate as training tools expose gradient statistics and progress measurements. Their value still needs evidence on the actual optimizer, model, and data rather than a borrowed threshold from another workload. Teams can keep a small set of batch experiments alongside learning-rate studies, revisit the choice when the training phase changes, and report both resource use and time to target. A reproducible comparison should preserve the target definition and include unsuccessful configurations so the apparent benefit is not based only on a selected run.
現実世界の実装
In a hypothetical experiment, batch 256 needs 4,000 updates to reach a target, while batch 512 needs 2,200. The second run uses fewer updates but processes 1,126,400 examples rather than 1,024,000.
A team doubles its batch again but sees almost no reduction in updates to the same target. It checks whether additional parallel work is providing useful optimization progress.
A researcher repeats a batch-size sweep later in training rather than assuming the best early-training batch remains best near the target loss.
Two configurations use the same global batch but different numbers of devices. The team compares elapsed time because communication and per-update execution can differ.
リスクとガードレール
1 つのベンチマークを最適化すると、より広範なシステムの弱点が隠れる可能性があります。
インフラストラクチャとメンテナンスのコストは過小評価されがちです。
システムが複雑になるにつれて、セキュリティと可観測性のギャップが拡大する可能性があります。
実装ロードマップ
実装前にレイテンシ、品質、コストの目標を定義します。
現実的な負荷とデータ条件でのベンチマーク。
エラー、ドリフト、ユーザーへの影響を計測器で監視します。
スケーリングの前に、ロールバックとインシデント対応のパスを準備します。
探検を続けましょう
Free newsletter
Get the daily AI briefing
Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.
One email each weekday. Unsubscribe in one click. We never sell or share your address.
Test yourself
Take the Critical Batch Size quiz
Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.
Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation
よくある質問
What is Critical Batch Size?
Critical batch size describes a transition in training efficiency: beyond it, larger batches give diminishing reductions in the number of updates needed to reach a target. It is a property of a training problem and performance target, not simply the largest batch that fits in accelerator memory. Choosing a batch also requires measuring elapsed time, total processed examples, and final task performance.
Which behavior characterizes batches far beyond a training problem’s critical batch scale?
The critical scale describes diminishing optimization returns from larger batches, not a universal inability to train.
Why is the largest batch that fits in memory not necessarily the critical batch size?
Critical batch size concerns training efficiency, while memory capacity is a separate practical constraint.
In the worked comparison, increasing the batch from 256 to 512 changes required updates from 4,000 to 2,200. What happens to processed examples?
The larger batch processes 512 × 2,200 = 1,126,400 examples, despite requiring fewer updates.
Which measurement is still needed before concluding that fewer training updates saved elapsed time?
Updates can take different amounts of time across batch sizes and device arrangements.
What statistic did the cited large-batch research connect with the largest useful batch range?
The research uses gradient noise scale as an empirical predictor of the critical batch range.
学び続ける
関連ガイド
このトピックのために選ばれたその他のガイド