3.2.11 · D5Training Deep Networks
Question bank — Early stopping
Before we start, three plain-word reminders so no symbol here is unearned:
Recall The vocabulary these questions assume
- Training loss — how badly the model fits the data it learns from.
- Validation loss () — how badly it fits held-out data it never trains on; our stand-in for "the real test."
- Patience () — how many epochs in a row of no improvement we tolerate before quitting.
- Checkpoint — a saved photo of the weights at some epoch, so we can roll back to it.
- Overfitting — memorizing quirks of the training set instead of general patterns (see Overfitting and Generalization).
- Eigenvalue — the "steepness" of the loss bowl along one special direction; big = steep = fast-learned (see Hessian and Curvature).
True or false — justify
The U-shaped validation curve means training loss also eventually rises.
False. Training loss keeps falling (the model can always fit its own data better); only validation loss makes the U-turn. That widening gap is exactly overfitting.
Early stopping is a form of regularization even though it adds no penalty term to the loss.
True. It regularizes implicitly by limiting how far weights travel from their small initialization; fewer steps = smaller effective weights = simpler function, mirroring L2 Regularization (Weight Decay).
Early stopping and weight decay are literally the same algorithm.
False. They are only approximately equivalent, and only under a quadratic approximation of the loss near a minimum. The match is , not an exact identity.
Training for more steps corresponds to stronger regularization.
False, it's the reverse. More steps play the role of growing, so (the effective decay) shrinks toward zero — more steps means weaker regularization and larger weights.
Once validation loss ticks up for the first time, the model has definitely started overfitting.
False. Validation loss is noisy (mini-batch stochasticity, small val set), so a single uptick is often a blip. That's why we wait epochs before trusting the rise.
If two runs stop at the same epoch, they must have the same amount of regularization.
False. Effective regularization also depends on the learning rate and the curvature per direction. The matching condition involves the product and the step count together, not alone.
Using validation accuracy instead of validation loss as the monitored metric never changes the stopping point.
False. Accuracy is flatter and noisier (it counts discrete correct/wrong), so it can plateau or jitter differently, triggering stops at other epochs than a smooth loss would.
Early stopping suppresses the high-curvature (large ) directions the most.
False, it's the low-curvature ones. Large- directions fit almost fully and fast; small- directions barely move in steps and stay near their small init — that's what gets suppressed.
The validation set can safely be reused as the test set once training finishes.
False. We selected the stopping epoch using validation loss, so it's no longer unbiased — it became part of the optimization. You need a separate untouched test set (see Validation and Cross-Validation).
Spot the error
"We stopped at epoch 8 because patience ran out, so we deploy the epoch-8 weights."
Error: deploy the best checkpoint, not the last. Epochs after the minimum are more overfit; you keep the lowest-validation-loss weights, which came earlier.
"Validation loss rose at epoch 4, so we stopped immediately — clean early stopping."
Error: stopping on the first rise ignores noise. With patience you'd have kept going and often found a better minimum at epoch 5.
"Since early stopping equals weight decay, we can drop and also skip choosing a learning rate carefully."
Error: the equivalence depends on the learning rate — sits inside . A bad breaks the approximation and can destabilize Gradient Descent entirely.
"Our validation set is 20 samples, which is fine because early stopping only needs a rough signal."
Error: a tiny val set makes so jittery it can swamp real improvements, causing premature stops or missed minima. Enlarge the set or raise patience.
"We set min-delta to so we only save on meaningful improvements — should stop cleanly."
Error: too-large min-delta treats genuine small gains as "no improvement," so the counter fills up early and you stop too soon (underfit).
"Restoring best weights is optional; the last weights are basically as good."
Error: past the minimum, every extra epoch drifts toward overfitting, so "last" is systematically worse than "best," not equivalent.
"The Taylor/quadratic argument proves early stopping regularizes for any loss surface."
Error: the proof assumes the loss looks like a bowl near a single minimum . Far from a minimum, or with many minima, the clean correspondence need not hold.
Why questions
Why does gradient descent capture broad patterns before noise?
Broad patterns reduce loss the most and fastest — they lie along high-curvature directions the optimizer descends first. Noise-fitting is what's left once the easy gains are used up.
Why must the validation set never influence gradient updates?
If it drove the weights, its loss would become optimistically biased and stop measuring generalization — it would just become more training data with no honest test signal left.
Why does limiting training time limit model complexity?
Fewer steps means weights stay closer to their small random init, and small weights encode a smoother, simpler function. Time budget becomes a complexity budget.
Why use patience rather than any fixed rule based on a single epoch?
A single epoch's validation loss is a noisy sample; patience averages out blips by requiring a streak of no improvement before believing the peak has passed.
Why does the number of steps act like ?
In the matched formula, large drives , which forces , i.e. . Small does the opposite. So and move inversely.
Why might early stopping and a good learning-rate schedule interact?
A decaying learning rate slows how fast each eigen-direction fits, so the same stopping epoch corresponds to a different effective regularization. The schedule reshapes what "stop at step " means.
Why keep a separate "best" checkpoint at all, instead of just remembering the epoch number?
Because the weights themselves are what you deploy; knowing "epoch 5 was best" is useless if those exact parameters were overwritten by later, worse epochs.
Edge cases
What happens if validation loss never rises within your epoch budget?
Early stopping never triggers; you either train to the budget's end or need more epochs. The U-shape's right arm simply hasn't appeared yet — you may be underfitting still.
What if the very first epoch already has the lowest validation loss?
The best checkpoint stays at epoch 1 and every later epoch fails to beat it, so you'll stop after epochs and restore epoch-1 weights — a sign the model overfits almost immediately (too flexible or too little data).
What does early stopping do along a direction with eigenvalue ?
The shrink factor , so stays at forever — that direction is fully suppressed, matching infinitely strong decay along a flat valley.
What if the learning rate is so large that ?
Then that eigen-direction grows instead of shrinking — gradient descent diverges there and the neat regularization interpretation collapses. Stability needs .
Two eigen-directions, one steep one flat, same stopping epoch — are both regularized equally?
No. At the shared , the steep ( large) direction is nearly fully fit while the flat one is barely moved, so early stopping applies different effective decay per direction — just like L2 Regularization (Weight Decay) does.
If you have very little data and can't spare a validation split, can you still early-stop?
Not cleanly by this method — you'd need cross-validation folds (see Validation and Cross-Validation) to estimate the U-curve, since without held-out data there's no honest signal for when generalization peaks.