Sibylla: To Retry or Not To Retry on Deep Learning Job Failure
summary
Sibylla classifies DL job failures as deterministic or nondeterministic by training RNN models (GRU/LSTM-like) on stdout/stderr logs and updating online with an auto-labeling majority-vote scheme. Dataset includes 97 operator logs and 159 manually collected logs (text-augmented). Simulations on the Microsoft Philly trace show avoiding retries for repeated deterministic faults cuts wasted GPU hours (deterministic = 5–23% of jobs, 12–20% GPU-hours) and improves cluster utilization and JCT by up to 15%, while lowering success rate by only about 0.06%.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:41Shared multi-tenant GPU clusters to
- 1:09Problem: Job failure of DL training
- 2:00Two types of job failures
- 4:03Opportunity on predictive retry
- 5:28Data source: stderr/stdout streams
- 6:22Sibylla: Text preprocessing
- 6:58Sibylla: Training phase
- 9:50Can Sibylla classify failure type well
- 10:44Can Sibylla improve cluster efficien
- 11:42Can Sibylla maintain job success ra
related talks
19mAnalysis of Large-Scale Multi-Tenant GPU Clusters for DNN Training Workloads
19mDynaRL: Flexible and Dynamic Scheduling of Large-Scale Reinforcement Learning Training
21mEnhancing Runtime Reliability in LLM Training via Fine-Grained Observability
31mReliable Data for Large ML Models: Principles and Practices
17mModel-Switching: Dealing with Fluctuating Workloads in Machine-Learning-as-a-Service
16mUnderstanding Stragglers in Large Model Training Using What-if Analysis
16mSLearn - A Case for Task Sampling based Learning for Cluster Job Scheduling
29mDemystifying Machine Learning in Production: Reasoning about a Large-Scale ML Platform
