2026-08-31

To contextualize this paradigm shift, the following matrix contrasts AdamW with the three leading next-generation architectures across their core mathematical mechanisms, memory overhead, latency profiles, and ideal deployment targets.
| Optimizer | Core Mathematical Mechanism | Memory Overhead per Parameter | Compute Latency Overhead | Ideal Architectural Target |
|---|---|---|---|---|
| AdamW | First-order adaptive learning rates via dense first (mean) and second (variance) momentum tracking. | High (2 additional buffers per parameter). | Baseline / Standard. | General-purpose baseline; highly stable across almost all architectures and downstream benchmarks. |
| Lion | Evolved sign-based momentum updates yielding uniform parameter update magnitudes. | Low (1 additional buffer per parameter). Saves up to 50% vs AdamW. | Slightly faster (fewer memory writes, up to 15% faster runtime). | Memory-constrained environments, massive batch sizes, and large-scale Vision Transformers / Diffusion models. |
| Sophia | Second-order clipped stochastic optimization using lightweight diagonal Hessian estimates. | Low (Hessian diagonals replace full variance tensors). Saves ~50% vs AdamW. | Minimal (Adds <5% average per-step overhead). | Billion-parameter Language Models seeking rapid pre-training convergence (2x speedup). |
| Muon | Momentum orthogonalization via Newton-Schulz iterations applied to 2D matrix weights. | Low (1 additional buffer for 2D parameters). | Moderate (Matrix operations add slight per-step compute, offset by rapid convergence). | 2D Transformer weights (Attention & MLP layers) requiring hyper-efficient sample alignment. |
To understand the structural pivot away from AdamW, one must first deconstruct the mechanical limitations of first-order stochastic optimization. First-order methods rely exclusively on the gradient (the slope) of the loss landscape. While AdamW improves upon basic Stochastic Gradient Descent (SGD) by scaling updates based on historical gradient variance, it remains fundamentally blind to the underlying curvature of the parameter space.
In highly dimensional spaces—such as the billions of parameters within an LLM—the loss landscape is notoriously jagged and heterogeneous. Some parameter dimensions exhibit sharp, steep cliffs, while others sprawl into flat, barren plateaus. AdamW attempts to navigate this by reducing the step size in steep dimensions and increasing it in flat ones, using its second-moment buffer. However, this buffer is purely a historical statistical artifact, not a true mathematical reflection of geometric curvature. Furthermore, dedicating roughly 66% of parameter-associated memory to optimizer states severely restricts the batch sizes and context windows that can be processed on a single Graphical Processing Unit (GPU). This friction has catalyzed three distinct evolutionary branches in modern optimization: memory-compressed heuristic discovery (Lion), scalable second-order approximation (Sophia), and gradient orthogonalization (Muon).
The first major departure from the Adam paradigm emerged not from human theoretical derivation, but from an automated symbolic program search via Google's AutoML [cite: 2]. The Lion optimizer, which stands for EvoLved Sign Momentum, was discovered by researchers utilizing Learning to Optimize (L2O) techniques, essentially employing algorithms to discover better algorithms across an infinite search space of mathematical operations [cite: 3, 4].
At its architectural core, Lion dramatically simplifies the optimization update rule. It discards the second-moment variance buffer entirely, relying solely on a momentum vector and a mathematical element-wise sign operation to determine the direction of the parameter update [cite: 3, 5]. Because Lion only maintains one momentum buffer, it operates with a significantly smaller memory footprint compared to AdamW, offering a 33% to 50% memory savings, making it highly attractive for large-scale, distributed deployments [cite: 2, 6].
The primary innovation of Lion is its use of the sign() function applied to a blended momentum-and-gradient estimate. This mathematical operation strips away the specific magnitude of the gradient, leaving only the directionality (positive or negative). Consequently, every single parameter in the network receives an update of uniform magnitude during a given step [cite: 4, 5]. This prevents any single parameter from being disproportionately altered simply because its gradient happened to exhibit a massive spike, acting as an implicit regularization mechanism that leads to convergence in smoother regions of the loss landscape and better generalization [cite: 4].
To implement Lion successfully, practitioners must heavily adjust traditional hyperparameters, as the uniform magnitude of sign-based updates alters the standard training dynamics. The following outlines the critical hyperparameter shifts required when migrating from AdamW to Lion:
| Hyperparameter | AdamW Standard | Lion Requirement | Architectural Reasoning |
|---|---|---|---|
| Learning Rate (LR) | Standard baseline (e.g., 1e-4) | 3x to 10x smaller | The sign operation inherently increases the mathematical norm of the update; smaller LRs prevent explosive divergence [cite: 7]. |
| Weight Decay | Baseline (e.g., 0.01) | 3x to 10x larger | Because effective weight decay is tied to the LR, reducing the LR requires scaling up decoupled weight decay to maintain regularization pressure [cite: 4]. |
| Batch Size | Highly variable (e.g., 256) | Optimal at 4096+ | Lion thrives on highly stable gradient estimates, scaling exceptionally well as batch sizes increase [cite: 4]. |
| Beta Parameters | (0.9, 0.999) | (0.9, 0.99) or (0.95, 0.98) | Lion uses two Exponential Moving Average (EMA) factors: one for tracking momentum, one for the update step. Lowering Beta2 reduces historical memorization [cite: 4]. |
| Learning Rate Warmup | Standard (e.g., 2k steps) | Larger (e.g., 8k to 32k steps) | Sign-based optimizers benefit significantly from extended linear warmup periods to stabilize early updates [cite: 8]. |
These hyperparameter constraints underscore that Lion is not merely a drop-in replacement, but a fundamentally different algorithmic entity. Theoretically, researchers have mapped Lion's behavior to the stochastic Frank-Wolfe algorithm for solving constrained optimization problems, bridging the gap between evolutionary discovery and formal information-theoretic frameworks [cite: 3]. In practice, fast PyTorch implementations utilizing fused ForEach operations have shown that Lion can be up to 15% faster in runtime than standard implementations, solidifying its position as a computationally lightweight powerhouse [cite: 6].
Lion has seen heavy integration into major deep learning libraries. In Keras 3 and TensorFlow, developers can invoke Lion directly via the built-in optimizer API, which intrinsically supports mixed-precision training and gradient accumulation:
import tensorflow as tfoptimizer = tf.keras.optimizers.Lion( learning_rate=1e-5, # 3x-10x smaller than AdamW beta_1=0.9, beta_2=0.99, weight_decay=0.1, # Larger than AdamW clipnorm=1.0 # Crucial for maintaining stability )
model.compile(optimizer=optimizer, loss='categorical_crossentropy')
In real-world production environments, Lion has been aggressively deployed within Google, specifically in their core search ads Click-Through Rate (CTR) models [cite: 3]. In these systems, memory constraints are exceptionally tight due to the sheer volume of embeddings and dense features processed simultaneously. By eliminating the variance buffer, Google is able to run significantly larger batches. Furthermore, when applied to billion-sample datasets like JFT and standard ImageNet classification utilizing Vision Transformers (ViT), Lion boosts top-1 accuracy by up to 2% while requiring fewer epochs to reach convergence [cite: 3, 5].
While Lion solves the memory bottleneck by discarding variance tracking entirely, another branch of research has pushed in the exact opposite direction: seeking to incorporate true second-order mathematical information without incurring computational ruin. In calculus, if the first derivative (the gradient) represents the slope of a hill, the second derivative (the Hessian matrix) represents the curvature of that hill.
In a mathematically perfect scenario, a neural network would use Newton's Method, dividing the gradient by the Hessian matrix to take flawless, curvature-adjusted steps. However, the Hessian for a billion-parameter LLM is a matrix with a trillion-squared elements, making its exact computation mathematically impossible on modern hardware. Previous attempts at second-order optimizers (such as AdaHessian or K-FAC) often crumbled when applied to massive, distributed, decoder-only Transformers due to extreme per-step overhead or violent numerical instability.
The optimizer Sophia (Second-order Clipped Stochastic Optimization) elegantly circumvents this impossibility through a synthesis of "lazy math" and strict numerical guardrails. Sophia acknowledges that chasing perfect mathematical curvature in the chaotic landscape of deep learning is a fool's errand. Instead, it relies on two foundational pillars: a lightweight diagonal Hessian estimate and an aggressive element-wise clipping mechanism [cite: 1, 6].
First, rather than computing the full Hessian, Sophia only estimates its diagonal elements, completely ignoring how parameter A affects parameter B. To compute this efficiently, it utilizes Hutchinson's Estimator (a stochastic method for approximating the trace of a matrix using random vectors) in a variant known as Sophia-H, or the Gauss-Newton-Bartlett (GNB) estimator [cite: 6].
To understand Hutchinson's Estimator, imagine trying to estimate the total volume of a colossal, irregularly shaped building. Instead of meticulously measuring every single brick and interior wall (which is computationally analogous to computing the full trillion-element Hessian), you randomly fire lasers through the building and measure their path lengths. By averaging these random, lightweight cross-sections, you get a highly accurate estimation of the total volume with a tiny fraction of the effort.
Crucially, Sophia only computes this estimate every handful of iterations (typically every 10 steps), heavily dampening the average per-step time and memory overhead so that it adds less than 5% average computational cost compared to first-order methods [cite: 1, 9].
The second pillar—clipping—is what prevents the catastrophic failures that have historically plagued second-order methods. When a traditional second-order optimizer enters a perfectly flat region of the loss landscape, the calculated curvature approaches zero. Dividing the gradient by a near-zero number results in a massive, explosive step that can throw the model parameters into the stratosphere, immediately resulting in NaN (Not a Number) errors. Sophia introduces a strict clipping mechanism that limits the worst-case update size, effectively bounding the update scale and taming the negative impacts of non-convexity [cite: 1, 6].
When migrating from AdamW to Sophia, operators must recognize that Sophia requires distinct hyperparameter calibrations:
| Hyperparameter | AdamW Standard | Sophia Requirement | Architectural Reasoning |
|---|---|---|---|
| Learning Rate (LR) | Standard baseline (e.g., 6e-4) | Half of AdamW or equal (e.g., 6e-4 to 7e-4) | Unlike Lion, Sophia's LR is directly comparable to AdamW, though it often tolerates a slightly higher or halved rate depending on the scale to drive faster convergence [cite: 10, 11]. |
| Rho (Maximum Update Size) | N/A | 0.01 to 0.1 (Typically 0.03 - 0.05) | This parameter is unique to Sophia and controls the clipping threshold. A larger Rho means more aggressive updates. It is highly transferable across model sizes (e.g., 0.03 works for both 125M and 335M models) [cite: 9, 10, 11]. |
| Weight Decay | Baseline (e.g., 0.01) | Slightly larger (e.g., 0.1 to 0.2) | Sophia benefits from a slightly more aggressive weight decay penalty due to its highly efficient curvature navigation [cite: 9, 11]. |
| Betas (Momentum) | (0.9, 0.999) | (0.965, 0.99) | Beta1 is the gradient moving average, and Beta2 tracks the Hessian moving average. These parameters closely mirror AdamW but require slight tweaks for optimal stability [cite: 9]. |
The empirical results of this architecture are striking. On generative pre-training tasks involving GPT-style architectures ranging from 125 million to 6.6 billion parameters, Sophia achieves a consistent 2x speed-up over AdamW [cite: 6]. It reaches the target validation perplexity in exactly 50% fewer optimization steps, leading to massive reductions in total computational cost and wall-clock time [cite: 6, 12]. However, it is important to note an underreported trade-off: while Sophia minimizes training loss fastest, models trained with AdamW sometimes edge out Sophia models on zero-shot downstream benchmarks like HellaSwag and PIQA when compute budgets are identical [cite: 1].
Beyond theoretical benchmarks on large language models, the Sophia framework is actively deployed in complex real-world robotics and neuro-symbolic simulation environments. It is a core component of the Sophia robot ecosystem—used in platforms like SophiaPop (human-AI music creation) and Sophia-in-Audition, which leverages multi-camera virtual production pipelines and neuro-symbolic control mechanisms [cite: 13]. Additionally, Sophia-SPGD (an adaptive variant of the Stochastic Parallel Gradient Descent algorithm utilizing Sophia's lightweight second-order mechanics) has been deployed in optics to dramatically improve convergence speed and accuracy in wavefront corrector voltage signals [cite: 12]. It also serves as the optimization backbone for computing energy-dependent cross-sections in time-dependent hadronic accelerator models [cite: 13].
While Sophia addresses generic neural network curvature and Lion simplifies momentum state, the Muon optimizer takes an aggressively specialized approach. Developed by Keller Jordan and popularized by Moonshot AI, Muon (MomentUm Orthogonalized by Newton-schulz) was designed with a highly specific structural observation in mind: the internal hidden 2D weights of a Transformer architecture behave fundamentally differently than 1D parameters like biases or layer normalizations [cite: 14, 15].
In practice, when updating the massive 2D matrix weights within attention layers and Multi-Layer Perceptrons (MLPs), the gradient updates tend to suffer from very high condition numbers (a mathematical measure indicating how highly skewed and sensitive a matrix is to error, meaning the matrix is nearly low-rank and dominated by a tiny handful of extremely large singular directions) [cite: 16]. Because AdamW treats every parameter scalar independently, it struggles to efficiently process these dense, interconnected matrix structures, often overshadowing rare but critically important update directions.
Muon directly addresses this high condition number by transforming the momentum matrix before applying the update. It computes the gradient of the 2D weight, calculates its momentum, and then applies a mathematical procedure known as Newton-Schulz iterations to orthogonalize the momentum matrix [cite: 14, 16].
To understand Newton-Schulz iterations, imagine an incredibly wobbly table where one or two legs are massively longer than the others (representing a highly skewed matrix). Instead of trying to measure and rebuild the entire table from scratch using complex geometry (which is computationally analogous to performing a slow Singular Value Decomposition or SVD), you use a specialized sander that iteratively shaves down only the longest points. After exactly five quick passes, the table stands perfectly flat. In linear algebra, Newton-Schulz is an iterative, division-free method that computes the inverse square root of a matrix using only fast hardware-level matrix multiplications, completely avoiding slow mathematical bottlenecks.
By forcing the matrix into an orthogonal state, Muon effectively equalizes all of the singular values within the update matrix (typically to 1) [cite: 16]. This "whitening" effect flattens the distribution of singular directions, forcefully amplifying the rare, nuanced update vectors that standard optimizers ignore, which leads to drastically improved sample efficiency during pre-training [cite: 14, 16].
The configuration of Muon is highly specific and requires a departure from standard Adam defaults. Below are the recommended hyperparameters for migrating to Muon:
| Hyperparameter | AdamW Standard | Muon Requirement | Architectural Reasoning |
|---|---|---|---|
| Learning Rate (LR) | Standard baseline (e.g., 1e-4) | Scaled by \(0.2\sqrt{d}\) (roughly 10x larger than AdamW) | Because Muon forces update matrices into an orthogonal state, the magnitudes change drastically. A simple rule of thumb for Muon variants is to multiply Adam's learning rate by 10 [cite: 14, 15]. |
| Momentum | 0.9 | 0.85 to 0.95 | Muon relies heavily on a strong momentum buffer to accumulate historical gradients before orthogonalization [cite: 14]. |
| Nesterov Momentum | False (Typically) | True | Nesterov momentum empirically performs better with Newton-Schulz iterations, acting as an intelligent look-ahead mechanism [cite: 14, 17]. |
| Newton-Schulz (NS) Steps | N/A | 5 | Five iterations represent the "sweet spot" for balancing computational overhead with perfect matrix orthogonalization [cite: 14]. |
| Head Group Size (Group Muon) | N/A | Tuned Granularity | Because multi-head attention operates on individual heads, applying Muon to the full matrix creates a granularity mismatch. Grouping a specific number of heads (\(g\)) before orthogonalization optimizes the gain-cost trade-off [cite: 16]. |
The speed and efficiency metrics associated with Muon are actively disrupting frontier AI development. In open-source nanoGPT speedrunning benchmarks, Muon improved training speed by 35% over AdamW [cite: 14]. Scaling up to a 1.5 billion parameter model, it reached GPT-2 XL level performance approximately 25% faster than AdamW. Because of its ~2x overall efficiency gain, Muon has been heavily adopted by top AI labs; it is the underlying optimizer for production-level LLMs such as Moonshot's Kimi-K2-Thinking model and Zhipu AI's 744-billion parameter GLM-5 [cite: 18].
The raw success of the base Muon optimizer has triggered an immediate cambrian explosion of derivative architectures designed to push matrix orthogonalization further, specifically targeting numerical instability and computational latency.
While standard Muon performs steepest-direction descent with respect to the spectral norm, researchers identified that it implicitly neglects certain preconditions tied to the input data. Specifically, standard Muon acts as an implicit Newton-type method but assumes the input data's second moment is approximately isotropic (uniform in all directions).
To correct this, a variant known as Newton-Muon was developed. This architecture injects an activation right-preconditioner before initiating the Newton-Schulz iterations. By accounting for the actual distribution of the input data's second moment, Newton-Muon converges significantly faster. Although computing the right-preconditioner adds a 1.8% higher per-step compute cost, it reduces the overall wall-clock time by roughly 4% and reaches baseline validation losses in 6% fewer steps compared to standard Muon.
A second major vulnerability of the original Muon optimizer lies in hardware-level arithmetic. When executing standard Newton-Schulz iterations using half-precision floating-point arithmetic (FP16 or BF16)—which is mandatory for modern LLM scale—the algorithm suffers from severe numerical instability [cite: 19].
Specifically, the limited bit-depth of half-precision truncates the tiny numerical differences that occur during continuous matrix multiplications. This low-precision truncation causes rapid "eigenvector drift", where small errors accumulate exponentially over the iterations. This manifests as spurious negative eigenvalues accumulating within the Gram matrix (a fundamental matrix formed by multiplying a set of vectors by their own transpose, effectively capturing all pairwise inner products). After just a few iterations, these negative eigenvalues blow up, causing the Gram matrix to explode and immediately crash the training run [cite: 19, 20].
To remedy this without falling back to slow, full-precision (FP32) arithmetic, researchers introduced Stabilized Gram Newton-Schulz, culminating in the GramMuon optimizer. GramMuon implements a sophisticated "restarting" strategy. By running Gram Newton-Schulz for only a few iterations and then systematically reconstructing the Gram matrix partway through the execution, the algorithm flushes out the numerical ghosts before they can grow large enough to destabilize the system [cite: 19, 20].
Furthermore, to address the high computational cost of the matrix orthogonalization step, GramMuon utilizes highly optimized custom GPU kernels written in CuTeDSL specifically for NVIDIA Hopper and Blackwell architectures. These handle symmetric matrix multiplication with unprecedented efficiency, resulting in a staggering 40% to 50% reduction in the runtime of the orthogonalization step itself. This achieves state-of-the-art optimization quality within 0.01 validation perplexity of standard Muon, effectively offering a true "free lunch" in performance gains [cite: 19, 20].
As noted, Muon's primary structural limitation is that it only handles 2D matrix parameters connected to dense inputs (such as attention projections and MLP layers). For all 1-dimensional parameters—such as the bias terms in linear layers, the gamma parameters in RMSNorm, the embedding matrices, and the final LM head—Muon fundamentally breaks down and will severely degrade performance if applied [cite: 14, 15]. Consequently, the standard operating procedure has been to configure training loops to use Muon for 2D weights and fall back to AdamW for 1D weights [cite: 14].
However, this creates a frustrating paradox: if the entire goal of transitioning away from Adam is to reduce the massive High Bandwidth Memory footprint consumed by second-moment variance buffers, keeping AdamW alive in the background for millions of embedding parameters defeats much of the architectural advantage.
This reality gives rise to the next logical evolution in AI infrastructure: Optimizer Hybridization. Rather than falling back to AdamW, cutting-edge training loops can be configured to completely purge first-order variance tracking from the stack by hybridizing highly specialized algorithms.
By deploying Muon strictly to handle the complex geometric updates of the 2D hidden layer matrices (benefiting from orthogonalization), and routing all remaining 1D parameters and embeddings to Lion (which only uses a sign-based single momentum buffer), engineers can theoretically eliminate AdamW entirely. This zero-Adam architecture combines the raw mathematical speed of Newton-Schulz orthogonalization with the extreme memory compression of evolved sign momentum. While this requires careful orchestration of varying learning rate schedules (since Muon requires 10x larger LRs and Lion requires 10x smaller LRs), the compounding benefits of reduced HBM allocation and accelerated convergence represent the frontier of scalable neural network training.
The epistemological shift away from standard first-order adaptive methods is not merely a trend, but a necessary evolution dictated by the physics of modern hardware and the geometry of deep learning loss landscapes. The unified, one-size-fits-all approach is rapidly dissolving into a new era of highly specialized, curvature-aware, and hardware-symbiotic optimization ecosystems.