TensorTau PathToAGI Training Deep Networks Level 07

Level 07 · Training Deep Networks · Chapter 096

Learning-Rate Schedules

Why should training take the same-size steps when it is far from a good solution and when it is making final refinements?

A fixed learning rate is simple. Schedules deliberately change ηt\eta_t over training.

1. Warmup

Large early updates can be unstable when activations, optimizer moments and representations are not yet settled. Warmup gradually raises the learning rate from a small value.

2. Decay

Later in training, smaller steps help refine the solution. Common schedules include step decay, exponential decay, cosine decay and polynomial decay.

Cosine decay has the form

ηt=ηmin+12(ηmax−ηmin)(1+cos⁡πtT).\eta_t=\eta_{min}+\frac12(\eta_{max}-\eta_{min})\left(1+\cos\frac{\pi t}{T}\right).

3. One-cycle intuition

Some schedules intentionally raise learning rate and then lower it, using large steps for exploration and small steps for convergence.

4. Count the right unit

Schedules may be defined per optimizer step, epoch or token. For large language models, “number of tokens processed” is often more meaningful than epochs.

5. Schedule and optimizer are coupled

A learning rate that works for Adam may not work for SGD. Changing batch size can also change a useful learning-rate range.

What to Remember

The learning rate is a trajectory, not necessarily one constant. Warmup manages early instability; decay supports later refinement.

Next → Weight Initialization: before the first optimizer step, how should millions of weights be chosen so signals can even travel through the network?

Six ways to work the chapter, climbing from explaining it in your own words to investigating it like a researcher. Reading is not enough — this is where the chapter lands.

  1. Explain: Warmup and decay.
  2. Calculate: Evaluate a cosine schedule at start, midpoint and end.
  3. Predict: What happens if the LR never decreases near convergence?
  4. Break: Remove warmup from a configuration that needs it.
  5. Build: Implement constant, step and cosine schedules.
  6. Investigate: Compare schedules using the same optimizer and total update budget.