Loss spikes the moment warmup ends: which hyperparameter is the prime suspect?
A LoRA fine-tune trains cleanly through 200 warmup steps, then the moment warmup finishes and the schedule hits its plateau, the loss jumps sharply and never recovers. Name the most likely knob, explain in one or two sentences why this exact failure mode points there, and describe the first remediation step.
Peak learning rate set too high for the regime. Warmup masks it; the moment the schedule reaches plateau, updates blow the parameters off the loss surface.
Imagine pushing a kid on a swing. You start with tiny taps so they get used to the rhythm, then settle into a steady push. If your steady push is way too hard, the swing flies up the chains and the kid bails out. The tiny early taps felt fine, but the steady push was always going to be too strong, you just could not see it during the gentle start. Training a model with warmup works the same way. The early steps are deliberately weak so the model can settle in. When the schedule hands over to the full peak rate, that rate is what your run actually experiences. If somebody copied a number from a different recipe, the gentle warmup gave no warning, and the plateau is where the wheels come off.
Detailed answer & concept explanation~8 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
5 min: warmup masks the peak + plateau handoff is the actual rate + regime-specific safe ranges + Adam state staleness + halve and rerun as first fix + longer warmup as secondary mitigation.
Real products, models, and research that use this idea.
- Llama 4 Maverick LoRA recipes in TRL and Unsloth default to peak LRs around 1e-4 to 2e-4; the same number plugged into a full fine-tune of the base reliably reproduces a post-warmup spike.
- DPO recipes on Claude Opus 4.7-style preference data routinely sit at 5e-7 to 5e-6 peak; an SFT-tuned 1e-5 dropped in causes a textbook divergence one step after warmup ends.
- Mistral and Qwen 3.5 QLoRA cookbooks set peak LR around 2e-4 with 3 to 10 percent warmup, precisely because higher peaks tip over at the plateau.
- Hugging Face TRL release notes call out the regime mismatch in the SFTTrainer to DPOTrainer migration, where users see the spike when they leave the SFT LR in place.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy does Adam's optimizer state become stale at the moment the peak engages?
QIf halving the peak LR helps but still leaves instability, what is your next move?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Blaming the scheduler or the dataset. The scheduler is doing exactly what it was told. The peak value it was told to ramp to is the actual problem.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.