Skip to content
Technology How it works Breeder — Hyperion Burner — Aegis Burner — MetroVolt AI-Native Architecture Magnets Fuel cycle Safety Roadmap
Solutions AI & Data Centers Defense & Government Grid & Baseload Neutron Detection Quantum
Learn Technical Library
Proof Publications Whitepapers Technical Library Open Science & Reproducibility The Honest Gates
Company About / Mission Leadership Environment Health & Safety Investors Careers Press Contact
3D Model
AI Architecture › L0 · Foundation
L0 · Foundation

Checkpointing and Fault Tolerance

How long-running Kronos simulations and training runs survive node failures without losing days of compute.

THE STACK · click to jumpL7Ecosystem & StrategyL6Experience & VisualizationL5Applications & CopilotsL4OrchestrationL3Twin Modeling & AIL2Data FabricL1Control PlaneL0Foundation▲tlmctl▼L0 · FOUNDATIONThe offline compute substrate — multi-physics & batch training.1Cloud HPCelastic burst2Bare-Metal ClusterGPU / CPU3Supercomputingmulti-physics runs4Batch Trainingmodel builds5Simulation FarmGrad-Shafranov · MHD6Object StorecheckpointsMACHINE TIETrains the models that ship UP to L3 — no real-time path to the machine.KRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORFOUNDATIONSHEET 02REV. 2026-08L0 · AI-NATIVE STACK
L0 · Foundation — its place in the stack (left, click any layer) and its internal components (right). Telemetry rises; control descends.

Long jobs will hit failures

L0 runs jobs that last hours to days across many nodes, and at that scale hardware failures are not exceptional but expected. A single node fault should never cost a whole campaign. Checkpointing and fault tolerance are what let long-running simulations and training runs survive failures and resume, rather than restart from zero.

Checkpointing

A checkpoint is a saved snapshot of a job's state, solver fields and iteration count, or model weights and optimizer state, written periodically to storage. If a node fails, the job restarts from the last checkpoint instead of the beginning. The checkpoint interval trades storage and I/O overhead against the amount of work lost on failure.

Tolerance strategies by workload

Different workloads tolerate faults differently. Monte Carlo is naturally resilient: histories are independent, so a lost batch is simply re-run and only its contribution is redone. Coupled solves and synchronous training are fragile: a lost rank stalls the whole job, so they lean on checkpoints and, where possible, elastic recovery that re-forms the job around a replacement node.

Checkpoints double as reproducibility anchors. A checkpoint plus the recorded environment and seeds lets a run be resumed or re-derived exactly, which ties fault tolerance to the broader reproducibility discipline. The same snapshot that survives a crash also lets an auditor replay from a known state.

Fault tolerance keeps both machines' study cadences reliable. A multi-day breeder gyrokinetic run or a burner stability campaign can complete despite node churn, and the scheduler's use of preemptible backfill depends on it: a preempted sweep job resumes from its checkpoint elsewhere with no scientific loss.

Content reviewed August 2026 · design-and-simulation stage