Papers for

data center operations teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

LLM pre-training dynamics often occur near critical learning stability points

Does LLM Pre-Training Typically Occur at the Edge of Stability?

Abstract: Quadratic approximations provide a common lens for studying neural network optimization, but recent evidence challenges their predictive validity. In full-batch gradient descent with learning rate (LR) $η$, Cohen et al. (2021) observed the Edge of Stability (EoS), where the largest Hessian eigenvalue concentrates near $2/η$, seemingly at odds with classical stability conditions predicted by quadratic approximations. In this work, we revisit the fidelity of quadratic approximations as a model of neural network training dynamics, with a particular focus on their failure modes in LLM training. We first highlight a distinct failure mode of the quadratic approximation, where persistent negative curvature causes the quadratic dynamics to diverge regardless of the LR, even though the real dynamics remain stable. We term this phenomenon the Edge of Convexity (EoC). After removing the effect of this LR-independent instability, we then propose a generalized definition of Edge of Stability (EoS) for stochastic training with adaptive optimizers, based on whether increasing the LR induces significant divergence in the quadratic dynamics while leaving the real dynamics largely unchanged. Across different LLM pretraining runs with various model sizes up to 787M, we find that (1) EoC is always observed across LLM pretraining, and (2) EoS is also prevalent but not universal: it disappears when the LR becomes sufficiently small (e.g., after decay) or when the batch size falls below a critical threshold that has a positive correlation with the critical batch size. Together, these findings characterize when and how quadratic approximations fail and provide a foundation for future work on understanding training dynamics.

Tue 27 OctMachine Learning
The gist
Training large language models (LLMs) involves adjusting many small parts to make them work better. Usually, researchers use a simple math tool called quadratic approximation to understand how these adjustments behave. The authors found that this simple tool sometimes doesn’t match what actually happens during training, especially with big models like LLMs. They identified two important behaviors during training—one that always happens and another that mostly happens depending on learning settings—which helps explain when these math tools fail and when they are useful.
Open → 2610.36778v1

Scheduler cuts wait times and improves fairness for HPC jobs

Bounding Queue Waits for Fair Scheduling of Bursty HPC Workloads via Hierarchical Algorithms

Abstract: HPC clusters are shared among many projects, each holding an allocation of node-hours, and ensuring fairness is becoming harder. Foundation models workflows and automated pipelines have made job submissions bursty and concentrated among a few heavy users, so occasional users absorb queueing delays created by frequent ones, with no indication of how long their jobs will wait. Existing schedulers either forget past usage, protect only the job at the head of the queue, or assume that running jobs can be preempted. We propose HyDRA, a Hybrid Deadline and Ranking-Aware scheduler that enforces fairness among users while bounding the queue wait of every job. HyDRA assigns each job a deadline on arrival based on its size, the priorities of its project and user, the current backlog, and how far its project and user are from their entitled share. It ranks waiting jobs by a priority score that grows with waiting time, serves jobs close to their deadlines first, and backfills a job only when no deadline, or fairness limit is violated. We evaluate HyDRA on workloads derived from a year of ALCF Polaris job traces, against conventional schedulers and variants inspired by PCS, Themis, and the PBS job-sort formula used at ALCF. HyDRA achieves $2\times$ the project-level Jain's fairness of the best baseline, starts 47\% of jobs by their deadlines compared with at most 36\% for the baselines even for largest workloads, and lowers the 95th-\%ile bounded slowdown by 4.2$\times$ relative to the next best baseline, at a moderate cost in utilization.

Fri 23 OctDistributed, Parallel, and Cluster Computing
The gist
High-performance computing (HPC) clusters run many projects that share computing resources, but some users submit lots of jobs all at once, causing delays for others. The authors created a new scheduler called HyDRA that gives each job a deadline based on fair resource use and other factors, then prioritizes jobs to minimize waiting times fairly. Their tests show HyDRA improves fairness between projects, lets more jobs start on time, and reduces long waits compared to existing methods.
Open → 2610.32027v1

Data loader method reduces idle time in distributed training by balancing workload

Coordination-Free Workload Regularization for Variable-Cost Distributed Training

Abstract: Synchronous data-parallel training usually assigns every rank the same number of records, even when record costs vary by orders of magnitude. For variable-length models, this converts input variation into idle time because each step waits for its most expensive rank-local batch. We present Batch Cost Lookahead (BCL), a coordination-free data-loading policy that buffers a bounded rank-local window and repartitions it into fixed-cardinality packs with balanced estimated cost. BCL preserves the trainer's record-count contract and requires neither cross-rank metadata exchange nor runtime modification. In simulation over public workload distributions, enabling BCL reduces per-rank estimated batch-cost variability by up to 82.8%. Across 13 NeMo-RL SFT corpora on eight H200 GPUs, rank-local BCL runs 1.050 to 1.167 times faster than pooled MFFD. Compiled H200 measurements on an internal sequence workload show speedups of 1.197 to 1.343 times over packed execution from one to four nodes. We also identify a memory-feasibility boundary: a p99 cap for high-variance or OOM-prone data bounds outliers before BCL balances the rest. These results show that substantial variable-cost imbalance can be removed at the data-loader boundary, while clarifying when data preparation or broader coordination is still necessary.

Thu 15 OctDistributed, Parallel, and Cluster ComputingMachine Learning
The gist
Training AI models across many computers can slow down when some computers get harder tasks than others. The authors found that by letting each computer look ahead at its upcoming work and reorganize it to balance how hard the tasks are, the overall training speeds up without needing extra coordination between computers. Their method keeps the amount of data each computer processes the same but evens out how much time each takes, cutting down waiting times. This improvement helps make large-scale AI training more efficient on modern hardware.
Open → 2610.21162v1

Custom network card cuts downtime and repairs in huge data centers

From ASIC to Fleet: Lessons from Building and Operating a Hyperscaler NIC

Abstract: We describe the operational infrastructure built to deploy and operate fbnic, a custom multi-host NIC, across hundreds of thousands of production hosts at Meta. Vendor multi-host NICs, designed by retrofitting single-host architectures, suffered from shared firmware and buffers that created cascading isolation failures over seven years. fbnic eliminates these through physical isolation, but shifting to in-house hardware shifts the entire operational burden to the hyperscaler. We present a hardware-in-the-loop CI pipeline testing firmware, driver, and kernel cross-products; a unified observability pipeline co-locating NIC and switch counters for cross-layer fault attribution; a driver-first architecture with fewer than ten firmware message types; a targeted firmware upgrade orchestrator at sub-sled granularity; and scoped repair automation confining blast radius to individual host slices. Over ten months, fbnic achieved a 12X reduction in unplanned unavailability, 37% lower mean time to repair, and 2.3X fewer hardware swaps compared to vendor NICs on the same platform.

Tue 6 OctNetworking and Internet ArchitectureHardware Architecture
The gist
Network cards help computers talk to each other inside huge data centers. The authors built a special network card called fbnic to fix problems with older cards that shared parts and caused big failures. They created new tools to test and watch over these cards and their software, making it easier to fix problems quickly and without affecting many computers. Using fbnic, the data centers had much less downtime, faster repairs, and fewer hardware replacements.
Open → 2610.07644v1

Training time efficiency improved for large recommendation systems

Optimizing Effective Training Time for Large-Scale Recommendation Systems

Abstract: Lifecycle overhead silently consumes accelerator capacity across large-scale recommendation training fleets. Our largest recommendation workloads process tens of billions train- ing examples per day on thousands of GPUs. Before this work, only 50-60% of their end-to-end wall time advanced training on new data. We present a fleet-scale study of this lifecycle overhead and a set of optimizations spanning the full training stack. We use Effective Training Time (ETT%) as an operational framework to instrument lost time, localize it to independently owned infrastructure components, and expose work repeated across job restarts. This analysis guides optimizations like communication elimination and pipeline overlap during trainer initialization; dynamic-shape handling, autotuning pruning, and reusable Py- Torch 2 compilation caches; asynchronous checkpointing; stan- dalone model publishing; and reductions in recovery cost. We evaluate the optimizations on representative models and measure their impacts in our training fleet. ETT% improves on every benchmark, by 15.5% on average, and reaches 85% on our largest workload. Fleet-wide ETT% rose from about 80% to above 90% after deployment.

Thu 1 OctInformation Retrieval
The gist
Training very large recommendation systems takes a lot of time on thousands of GPUs, but not all that time actually helps the computer learn from new data. The authors studied why so much time gets wasted and found ways to reduce it by improving how different parts of the system work together. These changes include smarter ways to handle data, reuse computations, and save progress without slowing everything down. After making these improvements, the systems spend much more of their time actually learning, up from about 80% to over 90%.
Open → 2610.02057v1