Choose a learning-rate policy by comparing update behavior and validating a complete training schedule rather than a single sweep result.
Problem
Context. The exact one-dimensional SGD fixture below isolates learning-rate behavior before considering noisy, scheduled training.
Task. Compare the three constant rates, explain convergence or divergence, and propose a controlled learning-rate selection procedure. Describe how warmup, decay, optimizer choice, and intended run length affect the final comparison.
Constraints. Use the stated loss, gradient, and starting point for the fixture; do not add momentum or stochastic noise. A short range test proposes candidates rather than proving the best full-run schedule.
Use plain SGD on , starting at with exact gradient . Compare constant rates , and . Which rates reduce the loss, and what changes when the intended run uses a schedule?
Candidate first, controlled run second
Choose the useful descent region, not the unstable end of the sweep
Derivation
Does crossing the minimum necessarily mean the iterations diverge?
Range-test references: Smith (2017) and the fastai learning-rate finder documentation.
Calculate the updates
For plain SGD, . Contraction requires , so .
| Rate | Decision | ||
|---|---|---|---|
| Reaches the minimum | |||
| Oscillates without progress | |||
| Diverges |
Finite values alone do not establish progress. The boundary rate never improves this loss. This calculation is not an Adam benchmark or a universal neural-network bound.
Test a candidate
Record the optimizer, loss reduction, batch, initialization, precision and intended training length. Use a disposable run to increase rates while recording loss and update behavior. For sweep steps, a geometric sweep can use
Choose a candidate in sustained descent, with margin before instability. Restore the starting model and optimizer state, then test the intended schedule on controlled runs. Compare representative validation results and stability at the same budget. A sweep changes weights along its path; its points are not independent rate trials.
Change the run
1. Double the curvature
New task: replace the loss by .
Picture and change: the gradient becomes . Recompute contraction from .
Check: the interval becomes . The old rate now oscillates without progress.
Use when: loss scaling, parameterization or optimizer changes the effective update.
2. Specify a shorter training horizon
New task: use steps, warmup steps, peak and final rate .
Picture and change: choose the schedule separately from the peak. At schedule position , use
Check: positions , , and give rates , , and .
Use when: the step budget changes. These fractions describe this fixture, not a universal schedule.
Do not continue from a failed sweep
Diverged weights and accumulated Adam moments are not a clean starting state. Reload model, optimizer and schedule state; control data order and randomness for the comparison. Otherwise a failed sweep can invalidate the candidate test.
Try changing the batch
Doubling batch size also changes loss reduction from mean to sum. What must be checked first?
Check your answer
Restore the intended reduction or account for its doubled gradient scale. Only then test a batch-scaling heuristic under controlled conditions.
Optimizer and training regime
Adam uses accumulated, coordinate-dependent moments, so its effective update is not simply plain SGD’s gradient times a rate. Batch-scaling rules require assumptions. Neither linear scaling for SGD nor square-root scaling for Adam is universal. The large-minibatch SGD recipe combines scaling with specific training conditions and warmup.
Fine-tuning must balance adaptation against preserving useful behavior. Compare layer updates and held-out behavior instead of assuming pretrained weights are well-conditioned. Fixed fine-tuning, SFT or preference-training rate ranges do not transfer automatically between models and objectives.
Schedules and diagnostics
Warmup limits early updates; its usefulness and mechanism depend on optimizer, parameterization and model. The Transformer schedule, cosine decay, step decay and one-cycle use different time profiles. Compare them at a stated training budget rather than declaring one always superior.
If every reasonable rate fails, inspect data, initialization, gradient scale, loss implementation and numerical precision. Reducing the rate does not repair incorrect labels or a broken backward pass.
Related: debug a model that is not learning and bias and variance.