Common issues and solutions when running AORTA benchmarks.
Solution: Install PyYAML or supply a JSON config instead.
pip install pyyaml
Solution: Install ROCm utilities or omit --enable-rocm-metrics.
Ensure ROCm tools are in your $PATH:
export PATH=$PATH:/opt/rocm/bin
Solution: Verify CUDA_DEVICE_MAX_CONNECTIONS=1 (set in launcher) to encourage overlap-friendly scheduling.
This is typically set automatically by the launch scripts, but you can verify:
export CUDA_DEVICE_MAX_CONNECTIONS=1
Solution: Increase dataloader.num_workers or reduce dataset volume.
torchrun --nproc_per_node 4 train.py \
--config config/default.yaml \
--override dataloader.num_workers=8
Cause: Launchers’ NPROC exceeds available GPUs.
Solution: The toolkit remaps surplus local ranks modulo the visible devices, but persistent failures usually indicate mismatched visibility.
Check your device visibility:
# CUDA
echo $CUDA_VISIBLE_DEVICES
# ROCm
echo $HIP_VISIBLE_DEVICES
Ensure the launcher’s --nproc_per_node matches your visible GPU count.
config/default.yaml to stress-test memory and communication pressureMixedPrecision modes via training.mixed_precision (none, fp16, or bf16)StreamProfiler.intercept_distributed_opsIf you encounter issues not covered here: