~/talk

Sibylla: To Retry or Not To Retry on Deep Learning Job Failure

Talkat USENIX ATC '22 · 2022-07-11..07-13· [machine-learning]
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
slides:none on file

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

  1. 0:00Intro
  2. 0:41Shared multi-tenant GPU clusters to
  3. 1:09Problem: Job failure of DL training
  4. 2:00Two types of job failures
  5. 4:03Opportunity on predictive retry
  6. 5:28Data source: stderr/stdout streams
  7. 6:22Sibylla: Text preprocessing
  8. 6:58Sibylla: Training phase
  9. 9:50Can Sibylla classify failure type well
  10. 10:44Can Sibylla improve cluster efficien
  11. 11:42Can Sibylla maintain job success ra
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.