All-reduce Also called: all reduceCombine values from every worker and give the combined result back to every worker.
An all-reduce applies a reduction, such as addition, across participating workers and returns the result to each one.
An intuition: everyone contributes a subtotal and receives the same grand total. Tensor-parallel layers use it to combine partial outputs. Communication volume depends on the collective algorithm; floating-point results can depend on reduction order.
Read in context: Tensor Parallelism’s Communication Boundary · Source or context
Checkpoint state Also called: optimizer stateThe saved state needed to pick up a process where it left off.
A training checkpoint may need model parameters, optimizer buffers, random-number-generator state, and other execution state. Saving only parameters may not be enough for exact continuation.
Read in context: 100 identical loss logs, 100 different model states · Source or context
Deterministic replay Also called: exact replayRerunning the same steps to check whether they lead to the same state.
A replay check fixes relevant inputs and execution conditions, then compares a rerun with a reference. Exact bits are stricter than similar loss or accuracy.
Read in context: 100 identical loss logs, 100 different model states · Source or context
GPU time-slicing Also called: time-slicingLet jobs take turns on a GPU rather than finish one job before starting the next.
GPU time-slicing suspends and resumes jobs so they share accelerator time. It can expose early feedback sooner while adding switching overhead and delaying some completions.
An intuition: give each experiment an initial turn before spending the whole afternoon on the first.
Read in context: When does GPU time-slicing speed up useful feedback? · Source or context
Microbatch Also called: microbatchesA smaller piece of a training batch that can move through pipeline stages.
A microbatch is one subdivision of a larger training batch. GPipe sends these pieces through layer partitions and accumulates their gradients before a synchronous update.
An intuition: smaller parcels keep an assembly line occupied instead of moving one oversized parcel at a time.
Read in context: How do microbatches change pipeline idle time? · Source or context
Pipeline bubble Also called: bubbleIdle time while a pipeline fills, drains, or waits for dependencies.
A pipeline bubble is unused stage time caused by the schedule’s dependencies. More microbatches can reduce fill-and-drain overhead relative to useful work, but an unevenly slow stage still limits progress.
An intuition: a station sits empty while it waits for the next parcel.
Read in context: How do microbatches change pipeline idle time? · Source or context
Reduction order Also called: floating-point reductionAdding the same numbers in a different order can change the last few digits.
Floating-point addition rounds intermediate results. Reordering a sum can therefore change low-order bits even when the same values are included.
Read in context: 100 identical loss logs, 100 different model states · Read in context: Why parallel sums disagree: tracing FP32 reduction order · Source or context
Statistical efficiencyHow much learning progress is obtained from the examples processed.
Statistical efficiency describes how effectively training examples contribute to progress. Larger batches can reduce gradient noise but need not provide proportionally more progress per update. Pollux models this alongside throughput.
An intuition: repeating a known example may consume effort without adding much information.
Read in context: Why can more training examples per second mean slower learning? · Source or context
Tensor parallelism Also called: tensor parallelSplit the computations inside a model layer across devices.
Tensor parallelism partitions a layer’s tensors and operations across workers. Some intermediate results stay local; others require communication before the next operation.
An intuition: several workers calculate different parts of one large worksheet, then combine the parts that the next step needs. The placement of nonlinear operations helps determine where communication is necessary.
Read in context: Tensor Parallelism’s Communication Boundary · Source or context
Training goodput Also called: goodputTraining throughput adjusted for how much useful learning the processed examples provide.
Pollux combines system throughput with statistical efficiency to estimate useful training progress per unit time. This differs from serving goodput defined by latency-qualified requests.
An intuition: count how much material is learned per hour, not merely how many pages are turned.
Read in context: Why can more training examples per second mean slower learning? · Source or context
ZeRO state sharding Also called: ZeRO, optimizer-state partitioningDivide training state across workers so each worker does not keep every copy.
ZeRO progressively partitions optimizer state, gradients, and parameters across data-parallel workers. Required pieces are communicated when needed.
An intuition: each worker owns part of a shared filing cabinet instead of a complete duplicate. Persistent-state savings do not include every activation, gathered parameter, or temporary buffer that contributes to peak memory.
Read in context: ZeRO’s Memory Budget, Byte by Byte · Source or context