Papers › Why Warmup the Learning Rate? Underlying Mechanisms and Improvements

Why Warmup the Learning Rate? Underlying Mechanisms and Improvements

13 Jun 2024arXiv:2406.09405archive 2025-07-28

Dayal Singh Kalra, Maissam Barkeshli

It is common in deep learning to warm up the learning rate η, often by a linear schedule between ηᵢₙᵢₜ = 0 and a predetermined target η_(trgt). In this paper, we show through systematic experiments using SGD and Adam that the overwhelming benefit of warmup arises from allowing the network to tolerate larger η_(trgt) {by forcing the network to more well-conditioned areas of the loss landscape}. The ability to handle larger η_(trgt) makes hyperparameter tuning more robust while improving the final performance. We uncover different regimes of operation during the warmup period, depending on whether training starts off in a progressive sharpening or sharpness reduction phase, which in turn depends on the initialization and parameterization. Using these insights, we show how ηᵢₙᵢₜ can be properly chosen by utilizing the loss catapult mechanism, which saves on the number of warmup steps, in some cases completely eliminating the need for warmup. We also suggest an initialization for the variance in Adam which provides benefits similar to warmup.

PaperPDFCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2406.09405")

Code

Syntology Ran 4 of 5 code samples harvested from 1 repository linked to this paper; 1 has no recorded run. Of those that ran: 4 ran with no contract checked.

By repository: found in paper text by Syntology: 5 samples from 1 repository, 4 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

dayal-kalra/why-warmup found in paper text by SyntologyMIT report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

5 samples harvested; 4 ran; 0 honoured the contract we drafted; 1 has no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

4ran
1unverified

Licence: 0 of the 5 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from dayal-kalra/why-warmup. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

cross_entropy_loss dayal-kalra/why-warmup/vision/mechanisms/utils/loss_utils.py found in paper text by Syntology ran fingerprinted MIT (permissive) · 26d13d6c867ba7fa · report
cross_entropy_loss_integer_labels dayal-kalra/why-warmup/vision/mechanisms/utils/loss_utils.py found in paper text by Syntology ran MIT (permissive) · b9ac929ad3f0fc94 · report
linear_warmup dayal-kalra/why-warmup/vision/mechanisms/train_resnet_grads_adam_lobpcg.py found in paper text by Syntology ran MIT (permissive) · facc696d7f68e5d0 · report
mse_loss dayal-kalra/why-warmup/vision/mechanisms/utils/loss_utils.py found in paper text by Syntology ran fingerprinted MIT (permissive) · 8294c2b79bb5a70f · report
count_parameters dayal-kalra/why-warmup/vision/mechanisms/utils/model_utils.py found in paper text by Syntology unverified MIT (permissive) · 5cdd8100958da566 · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AdamSGD

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections