A lower bound for stepsize-based acceleration of gradient descent
Abstract: Recent work has shown that, for smooth convex optimization, plain gradient descent can be accelerated from its textbook convergence rate of (where denotes the number of iterations) to using carefully designed stepsize schedules alone, without resorting to momentum or other algorithmic modifications. Despite this progress, however, little was known about lower bounds for such methods beyond the classical benchmark for general first-order methods. In this work, we present a new lower bound of for the last-iterate convergence rate of gradient descent with predetermined nonnegative stepsize schedules. This result provides rigorous evidence that stepsize schedules alone cannot accelerate plain GD to the optimal convergence rate. The proof was developed by GPT-5.6 Sol Pro under the authors' guidance.
Paper Prompts
Sign up for free to create and run prompts on this paper.
Top Community Prompts
Explain it Like I'm 14
1. What is this paper about?
This paper studies whether ordinary gradient descent can be made much faster just by changing its step sizes.
Gradient descent is a method for finding the lowest point of a bowl-shaped function. At each step, it moves in the direction that goes downhill:
1 |
new position = old position − step size × slope |
Usually, gradient descent uses the same step size every time. The paper asks:
If we plan all the step sizes in advance—including some unusually large steps—how quickly can gradient descent possibly work?
The paper focuses on smooth convex functions. In simple terms, these are functions shaped like bowls whose slopes do not change too suddenly.
2. Main research questions
The researchers are mainly trying to answer two questions:
- Can carefully chosen step sizes make ordinary gradient descent as fast as accelerated methods?
- Is there a limit to how much step-size planning alone can help?
For comparison:
- Standard gradient descent usually reaches an error of about $1/T$ after steps.
- Advanced methods using ideas such as momentum can reach about .
- Some recent studies found that ordinary gradient descent can improve beyond $1/T$ by occasionally taking very large steps.
This paper investigates whether step sizes alone can ever reach the ideal speed.
3. How the research was carried out
A planned step-size schedule
The paper assumes that the algorithm knows in advance how many steps it will take, say steps. Before starting, it chooses a complete list:
These step sizes must be:
- nonnegative,
- fixed before the problem is chosen,
- allowed to be in any order,
- allowed to include zero or extremely large values.
This is a very broad class of possible strategies.
Constructing a difficult problem
To test any proposed schedule, the researchers construct a special worst-case function designed to make that schedule perform poorly.
This is similar to designing a difficult obstacle course after seeing a runner’s planned moves. The function is still required to be a legitimate smooth, convex function, but it is chosen to expose weaknesses in the step-size plan.
Long steps and blocks
The researchers call a step “long” when its normalized size is larger than $1$. These long steps divide the algorithm’s journey into blocks.
The difficult function is built so that:
- the algorithm moves in one direction during each block,
- a long step sends it toward a new direction,
- the new directions are perpendicular to the earlier ones.
This creates a multi-dimensional “zigzag” path that prevents the algorithm from quickly reaching the minimum.
The construction uses a mathematical tool called a Moreau envelope. For a young reader, it is enough to think of this as a smoothing machine: it turns a possibly sharp geometric object into a smooth, bowl-like function while preserving the carefully designed behavior of the gradient.
The hard function is constructed in at most dimensions. This means the difficult example does not require an impossibly large space.
Removing dependence on the order of steps
The order of the long steps could make the analysis complicated. To handle this, the authors:
- Sort the long steps by size.
- Study the largest long steps.
- Represent their interactions as a path.
- Split the path into two sets of non-overlapping links, called matchings.
A matching is like choosing pairs of objects so that no object is used twice. This lets the researchers estimate the overall difficulty without worrying too much about the exact order in which the long steps appeared.
A growth and cutoff argument
Finally, the proof examines how the total size of the remaining steps changes as more large steps are considered. A special mathematical bookkeeping tool, called a Lyapunov potential, is used to show that the step-size schedule cannot keep improving indefinitely.
This eventually gives a lower bound on the final error.
4. Main findings
The central result is that for every exponent satisfying
there is always a smooth convex problem on which any predetermined nonnegative step-size schedule has final error at least
Here, means that the error cannot generally become smaller than a constant times .
In everyday language:
No matter how cleverly all the step sizes are planned in advance, there is always a smooth convex problem that prevents ordinary gradient descent from reliably reaching the ideal rate.
The result allows step sizes that are:
- zero,
- extremely large,
- arranged in any order,
- not necessarily chosen so that the function value decreases at every step.
This is important because it rules out many possible tricks based only on changing step sizes.
What the result does not prove
The paper does not completely determine the best possible rate.
The best known positive result says that certain specially designed schedules achieve approximately
The new lower bound says that one cannot improve all the way to approximately
or faster, in the precise sense described by the theorem.
Therefore, there is still a large gap:
| Result type | Exponent |
|---|---|
| Best known schedule-based improvement | About $1.2715$ |
| New impossibility threshold | About $1.9319$ |
| Ideal accelerated rate | $2$ |
The paper also does not quite prove the endpoint itself. It proves the result for every just larger than that number.
5. Why the findings matter
The usual accelerated methods reach the rate by adding extra ideas such as momentum. Momentum is like allowing a ball to keep some of its motion instead of deciding its movement only from the current slope.
This paper gives evidence that such extra ideas may really be necessary. Simply telling ordinary gradient descent to take short steps at some times and long steps at others is probably not enough to obtain the best possible speed.
The result is also valuable because it studies a very flexible setting. Earlier lower bounds often assumed that step sizes had a simple pattern or had to work for every possible stopping time. This paper allows a different schedule for each chosen number of steps and places almost no restrictions on the schedule.
Conclusion and potential impact
The paper shows that step-size planning alone has a fundamental limitation. Even with complete knowledge of the total number of iterations and permission to use very large steps, ordinary gradient descent can be forced to converge more slowly than the optimal accelerated rate.
The work does not yet identify the exact best exponent. However, it narrows the possibilities and strongly suggests that reaching the rate requires more than changing step sizes. Future research will need to close the gap between the known exponent of about $1.2715$ and the new lower-bound threshold of about $1.9319$, or discover a new method that determines the true limit.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
- The endpoint exponent remains unproved. The theorem establishes only for every , not the endpoint .
- The optimal convergence exponent is still unknown. The best known upper-bound exponent for predetermined stepsizes is , while the paper rules out exponents below approximately $1.9319$; the entire interval between these values remains unresolved.
- The silver-exponent conjecture is neither confirmed nor refuted. It remains unknown whether the optimal predetermined schedule achieves the exponent or whether a different, slower optimal exponent governs stepsize-only acceleration.
- No matching lower bound is available for the known accelerated schedules. The paper does not determine whether silver-ratio and related schedules are close to optimal, nor does it construct schedules that approach the lower-bound threshold .
- The finite-horizon optimal schedule is not characterized. There is no asymptotic description, closed-form construction, or certified optimization procedure for the best predetermined nonnegative schedule for arbitrary .
- The constants in the lower bound are not quantitatively characterized. The theorem guarantees a constant , but its dependence on is not optimized or evaluated in a way that would clarify the practical significance of the bound, especially as .
- The proof technique fails at the threshold because of a collapsing parameter interval. At , the matching argument requires an interval for that collapses to a point; it is unresolved whether a sharper matching estimate, a different decomposition, or a refined Lyapunov argument can overcome this obstruction.
- The worst-case performance of arbitrary schedules is not exactly characterized. The functional provides a lower-bound construction, but the exact minimax value over all schedules and smooth convex objectives is unknown.
- The constructed hard instances may not be extremal for the full function class. The Moreau-envelope construction certifies difficult instances within a particular geometric family, but it is unresolved whether these instances capture the true worst case for every schedule.
- The role of temporal ordering is not fully understood. The matching argument removes ordering dependence for purposes of a lower bound, but the paper does not identify which orderings are genuinely hardest or whether an ordering-aware analysis could substantially strengthen the exponent.
- The dimension dependence is not shown to be necessary. The hard instance uses dimension at most , but it is unknown whether comparable lower bounds hold in fixed dimension, low dimension, or dimension independent of .
- The result does not provide a lower bound for adaptive stepsizes. Stepsizes depending on observed gradients, function values, or iterates are excluded, so it remains unknown whether adaptive gradient descent without momentum can attain faster rates.
- Randomized stepsize strategies are not covered. The theorem applies to deterministic schedules fixed in advance; the minimax performance of randomized predetermined schedules remains open.
- Signed stepsizes are excluded. The analysis assumes , leaving unresolved whether allowing negative stepsizes can improve last-iterate convergence for smooth convex minimization.
- The result does not address output transformations. Averaging, extrapolation, or other post-processing of the iterates may achieve rates unavailable to the unmodified last iterate, but these possibilities are not analyzed for arbitrary long-step schedules.
- Intermediate-iterate behavior is left unexplored. Since the lower bound concerns only , it does not determine whether the same schedules can guarantee useful bounds for , averaged iterates, or cumulative objective error.
- The analysis does not establish a complete anytime-versus-horizon-dependent theory. The paper distinguishes prescribed-horizon schedules from anytime schedules, but the optimal tradeoff between knowing the horizon and requiring uniform performance over all stopping times remains unknown.
- Extensions beyond unconstrained smooth convex optimization are not established. It is unclear whether analogous lower bounds hold for projected gradient descent, proximal gradient methods, composite objectives, or other constrained settings.
- Strongly convex and nonconvex analogues are not derived. The paper does not determine whether predetermined long-step schedules face comparable limitations under strong convexity or under weaker/nonconvex smoothness assumptions.
- The relationship to gradient-norm guarantees remains unresolved. The lower bound concerns objective suboptimality only; it does not establish corresponding impossibility results for , stationarity measures, or other performance criteria.
- The effect of additional structural assumptions on the objective is unknown. The hard instances are nonspecific smooth convex functions, so the potential of stepsize-only acceleration on quadratic, separable, self-concordant, or otherwise structured objectives remains open.
Practical Applications
Immediate Applications
- Algorithm-selection guidance in convex optimization (software, machine learning, numerical optimization)
- Use the lower bound to avoid treating predetermined stepsize schedules as a substitute for genuinely accelerated methods. For smooth convex problems, plain GD with any fixed, nonnegative, horizon-dependent schedule cannot be certified—under the paper’s model—to achieve the optimal last-iterate rate.
- Actionable workflow: use standard GD or schedule-based acceleration for simplicity, but select Nesterov acceleration, Optimized Gradient, or another momentum-based method when an worst-case guarantee is important.
- Dependency: the result applies to convex objectives with an -Lipschitz gradient, known initialization radius , deterministic schedules fixed before seeing the objective, and the unmodified last iterate. It does not directly cover adaptive or randomized algorithms.
- A benchmark for stepsize-schedule design and evaluation (optimization software, research tooling)
- Implement the lower-bound exponent as a stress-test criterion for new schedule-generation methods. A schedule should be evaluated not only on representative objectives but also against adversarial smooth convex instances whose dimension can be as large as .
- Potential tool: a schedule-evaluation module that reports empirical worst-case performance, the number and magnitude of steps with , the capped mass , and the excess-step statistics used in the paper.
- Dependency: empirical tests cannot establish the theorem’s asymptotic guarantee; the adversarial instance depends on the chosen schedule and horizon.
- Safety checks for long-step implementations (software engineering, numerical computing)
- The paper shows that arbitrarily large nonnegative steps and temporary increases in the objective must be considered in worst-case analysis. Optimization libraries can therefore add warnings or diagnostics when a schedule uses stepsizes larger than $1/L$, especially when it assumes that objective values will decrease monotonically.
- Potential workflow: log normalized steps , flag excessive long steps, and compare terminal performance with a conservative baseline.
- Dependency: a long step is not necessarily harmful on every practical objective; the result is a worst-case impossibility statement, not a claim that all long-step schedules fail on typical data.
- Reproducible comparison of optimization algorithms (academia and industrial benchmarking)
- Report the prescribed horizon, whether the schedule depends on , whether steps may exceed $1/L$, the output criterion (last iterate versus average or best iterate), and whether adaptation or momentum is used. This prevents schedule-only acceleration from being compared ambiguously with accelerated first-order methods.
- Dependency: comparisons must normalize objective smoothness, initial distance, dimension, and oracle-call budget.
- Training and calibration guidance for convex machine-learning subproblems (machine learning, statistics)
- For convex models such as regularized least squares, some generalized linear models on bounded domains, and convex empirical-risk minimization, use the result as a reason to prefer momentum or adaptive methods when terminal accuracy is the primary target.
- Dependency: many modern learning objectives are nonconvex, stochastic, nonsmooth, or have unknown ; the theorem does not directly establish limits in those settings.
- Educational material for optimization courses and professional training (education)
- Use the result to illustrate the distinction between changing an algorithm’s update rule and merely changing its stepsizes. It provides a concrete example of why a method can improve over the textbook rate yet still fall short of the optimal rate.
- Potential product: lecture demonstrations or notebooks that compare constant-step GD, silver-ratio schedules, Nesterov acceleration, and adversarial Moreau-envelope examples.
- Dependency: the paper’s theorem is technical and currently leaves a gap between the best upper and lower exponents, so it should not be presented as a complete characterization.
Long-Term Applications
- Development of certified schedule-design software (optimization software and automated algorithm design)
- Combine the paper’s functional , matching bounds, and geometric hard-instance construction with performance-estimation-problem solvers. This could produce schedules that are provably near-optimal within the class of predetermined nonnegative GD schedules, rather than merely optimized on sampled quadratic objectives.
- Potential tool: a horizon-aware compiler that takes , an estimate of , and a desired output guarantee, then generates a schedule together with a certificate or adversarial test instance.
- Dependencies: the gap between the known upper exponent and the lower-bound threshold must be narrowed; global optimization over schedules may also be computationally difficult.
- Sharper impossibility results for optimization methods (academia)
- Extend the construction to determine whether the endpoint is valid and whether the actual optimal schedule-only exponent is closer to the silver exponent or to the lower-bound threshold.
- Potential outcome: a complete theory identifying the best possible convergence rate for predetermined schedules, which could guide the design of minimal-complexity optimization methods.
- Dependencies: the present proof only establishes the result for every , not at .
- Generalization to adaptive, randomized, signed, and feedback-controlled stepsizes (machine learning and theoretical computer science)
- Investigate whether the Moreau-envelope hard-instance technique can be adapted to schedules that depend on observed gradients, objective values, randomness, or previous iterates. This would clarify whether the limitation comes specifically from nonadaptivity or from the GD update itself.
- Potential applications: principled design of AdaGrad-like methods, line-search schemes, stochastic optimizers, and reinforcement-learning update rules.
- Dependencies: adaptive algorithms can potentially detect adversarial geometry; randomized schedules require a different notion of worst-case guarantee and may evade the deterministic construction.
- Extensions to constrained, proximal, and composite optimization (operations research, imaging, signal processing)
- Adapt the geometric construction to projected GD, proximal gradient, and other first-order methods. This could establish when stepsize manipulation alone is insufficient for problems involving constraints, regularizers, or nonsmooth composite terms.
- Potential tools: certified schedule policies for projected optimization, sparse regression, inverse problems, and distributed convex programs.
- Dependencies: the current hard instance relies on Euclidean projections onto a convex set and a smooth Moreau envelope; non-Euclidean geometry and nonsmooth terms may require new constructions.
- Robust optimization under uncertain smoothness estimates (engineering, finance, energy, and large-scale operations research)
- Develop schedules that remain safe when is estimated inaccurately or changes over time. Since the theorem allows arbitrarily large predetermined steps, it motivates studying robust schedules that trade nominal acceleration against protection from worst-case objective increases.
- Potential workflow: combine backtracking or online estimation with a fallback accelerated method rather than relying solely on a precomputed long-step schedule.
- Dependencies: the paper assumes a known fixed smoothness constant and a fixed horizon; time-varying, noisy, or locally smooth objectives are outside its formal scope.
- Applications to scientific computing and linear-system solvers (energy systems, simulation, robotics, control)
- Translate the distinction between spectral acceleration and general convex worst-case behavior into solver-selection rules. Long or fractal steps may be effective for structured quadratic systems, but the paper warns that such success does not automatically extend to arbitrary smooth convex models.
- Potential product: hybrid solvers that detect near-quadratic structure and use long-step schedules only in that regime, reverting to momentum or safeguarded methods otherwise.
- Dependencies: quadratic or strongly convex systems may have additional spectral information not assumed by the theorem, so the lower bound should not be interpreted as a universal limitation for conjugate-gradient-type methods.
- Policy and standards for optimization claims (public-sector AI governance, research policy, industrial compliance)
- Encourage reporting standards that distinguish worst-case theoretical rates from empirical speedups and specify whether acceleration comes from momentum, averaging, adaptivity, or a predetermined schedule.
- Potential policy use: evaluation protocols for safety-critical optimization in healthcare planning, finance, energy dispatch, and autonomous systems, where temporary objective deterioration or terminal-error guarantees may matter.
- Dependencies: the theorem concerns deterministic smooth convex minimization and cannot by itself set standards for stochastic, nonconvex, constrained, or multi-agent systems.
- Adversarial testing and robustness certification for optimization pipelines (healthcare analytics, finance, autonomous systems)
- Use the paper’s explicit low-dimensional hard instances as seeds for adversarial validation. A pipeline can be tested on convex objectives whose gradients follow the orthogonal-block structure induced by the Moreau envelope, including schedules with zero, reordered, or extremely large steps.
- Potential workflow: generate a schedule-specific adversarial objective, run the production optimizer, and verify terminal error, stability, and sensitivity to horizon mis-specification.
- Dependencies: the constructed instance may require dimension up to and is tailored to the schedule, so its realism for a particular application must be established separately.
Glossary
- Adversarial instance: A deliberately constructed problem instance designed to make an algorithm perform poorly. “the adversarial instance may depend on both”
- Ambient dimension: The dimension of the vector space containing the optimization variables. “ is a positive integer denoting the ambient dimension.”
- Anytime schedule: A single infinite stepsize sequence intended to work for every possible stopping time. “the ‘anytime’ setting, where a single infinite stepsize schedule must be fixed in advance”
- Block decomposition: A partition of an iteration schedule into consecutive groups separated by selected steps. “These indices identify long steps and partition the remaining iterations into the following gaps”
- Capped component: The portion of a stepsize truncated at a specified maximum, here one. “we decompose each into a capped component ”
- Chain value: A product-based quantity associated with a sequence of connected transition factors. “a chain value depends on the temporal order of the long steps”
- Convex hull: The smallest convex set containing a given collection of points. “Let ”
- Convex interpolation: The construction of a smooth convex function satisfying prescribed values or gradients at specified points. “Building on smooth interpolation”
- Cutoff argument: An analysis that divides ranked quantities at a selected threshold to derive a bound. “The proof now scans the ranks until either the favorable matching alternative occurs”
- Deterministic first-order method: An optimization algorithm that uses only first-order information and has no randomness. “The classical lower bound for deterministic first-order methods”
- Euclidean projection: The point in a closed convex set closest to a given point under Euclidean distance. “Write for the Euclidean projection of onto .”
- First-order oracle: A procedure that provides objective values and first derivatives to an optimization algorithm. “it applies to the entire class of first-order methods that access the objective only through a first-order oracle”
- Fractal ordering: A recursively structured ordering of steps intended to improve numerical stability. “Fractal orderings of these steps further improve intermediate stability”
- Geometric mean: The th root of the product of positive quantities. “If denotes the resulting geometric mean cost per edge”
- Gradient-feedback method: An adaptive optimization method whose stepsizes depend on observed gradients. “Gradient-feedback and AdaGrad-type methods use adaptive stepsizes”
- Hard instance: An optimization problem constructed to attain or demonstrate a worst-case lower bound. “we construct an explicit hard instance tailored to selected long steps”
- Horizon-dependent schedule: An algorithmic schedule chosen using the prescribed total number of iterations. “The strongest known constructions are based on the silver ratio”
- Information-based minimax risk: The smallest worst-case error achievable when methods are limited to a specified amount of information. “the exact information-based minimax risk also scales on the order of ”
- Interpolation: The existence or construction of a function consistent with prescribed values, gradients, or other constraints. “Building on smooth interpolation”
- Last-iterate convergence: Convergence measured using the algorithm’s final iterate rather than an average or best intermediate iterate. “Our lower bound concerns the convergence rate of the last iterate ”
- Lyapunov estimate: A bound obtained from a potential function whose change controls the evolution of an algorithm or recurrence. “Third, we combine a rank cutoff argument with a Lyapunov estimate”
- Mass-ratio identity: An exact relation connecting successive residual masses in the ranked schedule analysis. “Telescoping its one-step drift and using the mass-ratio identity”
- Matching: A set of pairwise disjoint edges in a graph, with no shared vertices. “The odd and even edges of this path form two matchings.”
- Moreau envelope: A smooth approximation of a function formed by minimizing it plus a quadratic distance penalty. “define the hard instance as the Moreau envelope of the support function of ”
- Moreau identity: A relationship connecting the gradient of a Moreau envelope with a projection operator. “The key property of this choice is the Moreau identity”
- Monotonicity assumption: An assumption that a sequence or objective value consistently increases or decreases. “no descent or monotonicity assumptions”
- Oracle lower bound: A lower bound applying to every algorithm restricted to a given oracle model. “Since this is an oracle lower bound”
- Orthogonal anchor: A specially constructed point aligned with a coordinate direction orthogonal to other such directions. “The construction places orthogonal anchors”
- Orthonormal basis: A set of mutually perpendicular unit vectors spanning a vector space. “where is an orthonormal basis”
- Performance estimation problem (PEP): An optimization framework for computing exact worst-case performance of first-order methods. “studies the exact worst-case performance of first-order methods through the performance estimation problem (PEP) framework”
- Proximal operator: The point minimizing a function plus a squared-distance regularization term. “We also define the corresponding proximal operator”
- Rank cutoff: A selected rank used to separate dominant schedule components from the remaining ones. “Rank cutoff and mass growth.”
- Residual schedule mass: The schedule mass remaining after excluding a specified number of the largest excesses. “We call the residual schedule mass at rank .”
- Support function: A function that assigns to a vector the maximum inner product with points in a set. “we define its support function by”
- Silver exponent: The exponent associated with the silver ratio that characterizes a particular accelerated convergence rate. “the optimal answer is given by the silver exponent”
- Silver ratio: The quadratic irrational number , used here to define an acceleration exponent. “The strongest known constructions are based on the silver ratio”
- Semidefinite program (SDP): An optimization problem over positive semidefinite matrices subject to linear constraints. “the PEP can be formulated as a finite-dimensional semidefinite program (SDP)”
- Smooth interpolation: Interpolation subject to smoothness and convexity constraints on a function and its gradients. “Building on smooth interpolation”
- Stepsize schedule: A sequence specifying the multiplier used for each gradient update. “ is the stepsize schedule.”
- Strongly convex: Having curvature bounded below by a positive quadratic function. “the objective is strongly convex in .”
- Suboptimality gap: The difference between the objective value at an iterate and the minimum objective value. “The empty selection contributes ; in particular, it already yields an gap”
- Support functional: A linear functional evaluated through maximization over a set, often represented by a support function. “the prescribed block gradient is the Euclidean projection onto ”
- Terminal objective value: The objective value attained at the final iteration. “the exact worst-case formula for the terminal objective value”
- Time-invariant stepsize: A stepsize that remains constant across all iterations. “restricting GD to time-invariant stepsizes”
- Variational inequality: An inequality characterizing an optimality or projection condition over a feasible set. “these are exactly the variational inequalities characterizing Euclidean projection”
- Worst-case convergence rate: The slowest rate guaranteed uniformly over all functions and initial conditions in a specified class. “for the worst-case last-iterate convergence rate of gradient descent”
- Worst-case objective gap: The largest possible difference between an algorithm’s objective value and the optimum over an allowed problem class. “the largest terminal objective gap attained within the family of instances”