dcp_save_interval
Controls how often full training state (weights and optimizer) is checkpointed using DCP (Distributed Checkpoint) format.
When set to
0 (the default), no periodic DCP checkpoints are written for resume. A successful run still saves final resumable training state by default. Sampler snapshots alone preserve weights but not optimizer state.
When set to a positive integer N, a full DCP checkpoint is written every N steps.
Why this matters: An interrupted run can resume only from saved training state. Enable periodic saves to bound lost progress; weights-only initialization starts a fresh optimizer.
Example (cookbook Config)
Config dataclass for its checkpoint fields.
Job recovery and preemption
For transient control-plane or worker interruptions, the trainer job manager exposesreconnect_and_wait so your driver can wait for a resumable state and resume cleanly.
load_state_with_optimizer() only restores optimizer state from DCP-format checkpoints. HF or sampler snapshots are not resumable optimizer checkpoints. Always load from the path returned by save_state() when you need full optimizer restore. See Saving and loading.Metrics reference
Policy and inference diagnostics
The default GRPO recipe has no reference model or reference-KL penalty. A small
policy-ratio diagnostic on an on-policy batch is expected; it does not measure
divergence from a frozen base model. Client request timings include transport
and queueing and can overlap, so compare the full optimizer window separately
from trainer execution time. Metric definitions and reductions live in the
step-metrics skill.