Time per epoch measures the average elapsed time needed to complete one full pass through the training data. Use it to estimate training timelines and compare scalability across hardware or training strategies. section 7.2.3 section 7.3.2
Apply the metric as a practical benchmarking signal:
- Benchmark it on a representative dataset to establish a baseline for predicting experimentation and project timelines. section 7.3.2
- Read it alongside memory utilization, FLOP/s, and time to convergence rather than treating runtime as the only scalability constraint. section 7.2.3 section 7.3.2
- Use changes in the metric to evaluate whether distributed training justifies its added complexity, debugging effort, and compute cost. section 7.8.2
DDP feasibility study
A team evaluating Distributed Data Parallelism tracks convergence time and average time per epoch during a one-week feasibility study. The measurements support a data-driven decision about deployment before committing additional resources. section 7.8.2
