ai-accelerator-training-eval
Benchmarking the Performance and Energy Efficiency of AI Accelerators for AI Training — Wang et al. (2019) (arXiv:1909.06842, 2019)
What this evaluates
Evaluates the computational performance and energy efficiency of various AI accelerators (CPUs, GPUs, TPUs) across standard deep learning workloads, including CNNs and NLP models. It measures how hardware architecture, numerical precision, and batch size impact training throughput and power consumption.
Datasets
- Standard DNN Workloads (ResNet50, Inception v3, Vgg16, LSTM, Deep Speech 2, Transformer) — total ?; splits: test (-1)
Metrics
throughput (primary) — range: other
- End-to-end training performance measured as throughput (samples/sec or images/sec), calculated by dividing the total processed samples by the wall-clock execution time. Also reports operator-level TFLOPS and hardware utilization (%).
TFLOPS — range: other
- Tera floating-point operations per second, computed by dividing the total FLOPs of the operator or model by the execution time.
energy_consumption — range: other
- Total energy used during end-to-end training, calculated as the integral of power draw over the training duration (typically measured in Joules).
Input / output format
Input: DNN architecture configuration, hardware accelerator type, numerical precision (FP32/Mixed), and mini-batch size.
Output: Throughput/TFLOPS values, hardware utilization percentages, and total energy consumption (Joules) for end-to-end training runs.
Scoring recipe
def evaluate_accelerator(model, hw, batch_size, steps):
start = time()
run_training(model, hw, batch_size, steps)
duration = time() - start
energy = measure_power(hw) * duration
throughput = (batch_size * steps) / duration
tflops = compute_model_flops(model) / duration
utilization = tflops / peak_tflops(hw)
return throughput, tflops, energy, utilization
Common pitfalls
- Hardware performance is highly sensitive to software stack optimizations (e.g., CUDA vs ROCm, Tensor Core utilization), which vary significantly across vendors and can skew cross-platform comparisons.
- Batch size selection critically impacts throughput and energy efficiency; suboptimal batch sizes can mask hardware capabilities, cause memory bottlenecks, or lead to misleading energy-per-sample metrics.
- Energy measurements must account for full system power draw, not just accelerator TDP, to reflect real-world efficiency and avoid underestimating cooling/power overhead.
Evidence (verbatim from paper)
We evaluate the AI Accelerators on the two major operators (i.e., matrix multiplication and 2D convolution) that are computation-intensive and widely used in DNN training. Computation-intensive operations call high-throughput kernels for calculating to achieve the highest FLOPS (throughput), as can be seen from Fig. 6.
Citation
@misc{wang2019benchmarking,
title={Benchmarking the Performance and Energy Efficiency of AI Accelerators for AI Training},
author={Wang et al. (2019)},
year={2019},
note={arXiv:1909.06842}
}
1---2name: ai-accelerator-training-eval3description: Evaluates the computational performance and energy efficiency of various AI accelerators (CPUs, GPUs, TPUs) across standard deep learning workloads, including CNNs and NLP models. It measures how hardware architecture, numerical precision, and batch size impact training throughput and power consumption. Use when the user wants to benchmark on Standard DNN Workloads (ResNet50, Inception v3, Vgg16, LSTM, Deep Speech 2, Transformer), or asks about evaluating this task. Reports throughput.4---56# ai-accelerator-training-eval78> Benchmarking the Performance and Energy Efficiency of AI Accelerators for AI Training — Wang et al. (2019) (arXiv:1909.06842, 2019)910## What this evaluates1112Evaluates the computational performance and energy efficiency of various AI accelerators (CPUs, GPUs, TPUs) across standard deep learning workloads, including CNNs and NLP models. It measures how hardware architecture, numerical precision, and batch size impact training throughput and power consumption.1314## Datasets1516- **Standard DNN Workloads (ResNet50, Inception v3, Vgg16, LSTM, Deep Speech 2, Transformer)** — total ?; splits: test (-1)1718## Metrics1920- `throughput` **(primary)** — range: other21 - End-to-end training performance measured as throughput (samples/sec or images/sec), calculated by dividing the total processed samples by the wall-clock execution time. Also reports operator-level TFLOPS and hardware utilization (%).22- `TFLOPS` — range: other23 - Tera floating-point operations per second, computed by dividing the total FLOPs of the operator or model by the execution time.24- `energy_consumption` — range: other25 - Total energy used during end-to-end training, calculated as the integral of power draw over the training duration (typically measured in Joules).2627## Input / output format2829**Input**: DNN architecture configuration, hardware accelerator type, numerical precision (FP32/Mixed), and mini-batch size.3031**Output**: Throughput/TFLOPS values, hardware utilization percentages, and total energy consumption (Joules) for end-to-end training runs.3233## Scoring recipe3435```python36def evaluate_accelerator(model, hw, batch_size, steps):37 start = time()38 run_training(model, hw, batch_size, steps)39 duration = time() - start40 energy = measure_power(hw) * duration41 throughput = (batch_size * steps) / duration42 tflops = compute_model_flops(model) / duration43 utilization = tflops / peak_tflops(hw)44 return throughput, tflops, energy, utilization45```4647## Common pitfalls4849- Hardware performance is highly sensitive to software stack optimizations (e.g., CUDA vs ROCm, Tensor Core utilization), which vary significantly across vendors and can skew cross-platform comparisons.50- Batch size selection critically impacts throughput and energy efficiency; suboptimal batch sizes can mask hardware capabilities, cause memory bottlenecks, or lead to misleading energy-per-sample metrics.51- Energy measurements must account for full system power draw, not just accelerator TDP, to reflect real-world efficiency and avoid underestimating cooling/power overhead.5253## Evidence (verbatim from paper)5455> We evaluate the AI Accelerators on the two major operators (i.e., matrix multiplication and 2D convolution) that are computation-intensive and widely used in DNN training. Computation-intensive operations call high-throughput kernels for calculating to achieve the highest FLOPS (throughput), as can be seen from Fig. 6.5657## Citation5859```bibtex60@misc{wang2019benchmarking,61 title={Benchmarking the Performance and Energy Efficiency of AI Accelerators for AI Training},62 author={Wang et al. (2019)},63 year={2019},64 note={arXiv:1909.06842}65}66```6768- arXiv: 1909.06842