Mostafa Elhoushi, Alex Pretko, Nolan Dey, Bin Claire Zhang, Gavia Gray, Gurpreet Gosal, Abdulrahman Mahmoud, Shane Bergsma, Joel Hestness
This is a slightly extended version of the paper published at ICML 2026
Properly configured layer dropout (stochastic depth) should be restored to state-of-the-art LLM pretraining, because it cuts training FLOPs (up to 25%) at equal or better validation loss and enables post-training inference speedups (up to 1.5x) with negligible accuracy loss.
More than 2400 pretraining runs on Cerebras CS-3 systems, decoder-only Celerity-style transformers, spanning 271M to 8.2B parameters (systematic sweeps up to 3.9B/116B tokens, larger confirmatory runs at 8.2B/160B tokens), at compute-optimal 20 tokens-per-parameter budgets, varying dropout rate, granularity, depth-wise distribution, temporal schedule, and jointly tuned optimizer hyperparameters (learning rate, batch size, weight decay) via muP/CompleteP transfer.
At equal training FLOPs, optimal layer dropout yields lower validation loss than dense baselines; for a fixed number of steps, up to 25% training FLOP savings at similar or lower loss. Inference: up to 1.5x speedup via early exit, intermediate-layer skipping, and self-speculative decoding with negligible accuracy loss. The key enabling detail is the scaling factor r_train = 1/rho, which allows one set of optimizer hyperparameters to transfer across dropout rates. The largest fully controlled sweeps are at a few billion parameters and ~100B tokens, below frontier scale.
The authors concede that prior degradations may reflect suboptimal schedules/hyperparameters rather than fundamentals, and their own earlier work reported accuracy degradation with naive layer dropout. Unstated: all experiments use one architecture family (ALiBi, squared ReLU), one dataset mix, one hardware vendor (Cerebras), and single-epoch 20 TPP regimes; the largest aggressive-dropout demonstration (8.2B) is small by frontier standards, and wall-clock speedups depend on hardware that can exploit per-sequence layer skipping.
Results are loss-based on an in-house model family and corpus rather than frontier benchmarks or third-party replication; the headline 25% FLOP savings and 1.5x inference speedup are best-case numbers from tuned configurations, not average gains; 271M to 8.2B is far from frontier scale so extrapolation to trillion-parameter training is untested; and Cerebras, which sells the hardware this method favors, published it, so incentive alignment warrants caution.
If the results transfer to frontier scale, training-time compute per capability unit falls and a single pretrained checkpoint can serve multiple latency/price tiers, modestly reinforcing the trend of falling inference cost per unit of capability and softening compute-demand growth. But at the scale tested this is a training-recipe efficiency result with no demonstrated frontier deployment yet, so its near-term economic significance is uncertain.
Technical Capability: Practitioners planning pretraining budgets get a concrete recipe (increasing depth distribution, decreasing schedule, 1/rho scaling) that claims real FLOP savings and depth-elastic deployment from one checkpoint.
Market & Valuation: Investors in compute-demand theses should note that training-recipe efficiency gains like this are one route by which capability per FLOP rises faster than raw compute scaling, pressuring capex-justification narratives at the margin.