Scheduling computational workflows on failure-prone platforms - - PowerPoint PPT Presentation

scheduling computational workflows on failure prone
SMART_READER_LITE
LIVE PREVIEW

Scheduling computational workflows on failure-prone platforms - - PowerPoint PPT Presentation

Scheduling computational workflows on failure-prone platforms Guillaume Aupy, Anne Benoit, Henri Casanova & Yves Robert Joint Lab, Nov. 2014 Workflow Motivation scheduling with failures G. Aupy Motivation Many HPC applications can be


slide-1
SLIDE 1

Scheduling computational workflows on failure-prone platforms

Guillaume Aupy, Anne Benoit, Henri Casanova & Yves Robert

Joint Lab, Nov. 2014

slide-2
SLIDE 2

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

1

Motivation

Many HPC applications can be represented as a computational workflow: Represented by a DAG:

◮ Vertices are tightly

coupled parallel tasks

◮ Edges represent data

dependency

  • Eg. CyberShake workflow (used to

characterize earthquake hazards) as presented by Pegasus.

slide-3
SLIDE 3

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

2

1 Motivation 2 Models

Platform Fault-tolerance Application

3 Results

Computation of the expected makespan NP-hardness, polynomial algorithms for special graphs

4 Efficient heuristic evaluation

Heuristics Evaluation

5 Conclusion

slide-4
SLIDE 4

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

3

Platform and processor assignments

Failure-prone platform:

◮ p processors ◮ Exponential failure distribution, MTBF: µ = 1

λ

slide-5
SLIDE 5

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

3

Platform and processor assignments

Failure-prone platform:

◮ p processors ◮ Exponential failure distribution, MTBF: µ = 1

λ

Mixed parallelism is hard. Even without failures.

◮ Assignment of processors to tasks? (throughput) ◮ Traversal of the graph? (scheduling) ◮ Data redistribution? (model redistribution cost)

slide-6
SLIDE 6

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

3

Platform and processor assignments

Failure-prone platform:

◮ p processors ◮ Exponential failure distribution, MTBF: µ = 1

λ

Mixed parallelism is hard. Even without failures.

◮ Assignment of processors to tasks? (throughput) ◮ Traversal of the graph? (scheduling) ◮ Data redistribution? (model redistribution cost)

Simplified scenario

Each task uses all available processors; workflow is linearized.

slide-7
SLIDE 7

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

4

Fault tolerance

We use the checkpoint technique for fault-tolerance. Checkpointing within tasks is expensive or hard:

◮ Expensive: for application-agnostic checkpoint, need to

checkpoint the full image

◮ Hard: modifying the implementation of the tasks to checkpoint

  • nly what is necessary

Checkpoint model

We only checkpoint the output data of tasks.

slide-8
SLIDE 8

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

5

Application model

Given a DAG: G = (V , E). For all tasks Ti, we know: wi: their execution time ci: the time to checkpoint their output ri: the time to recover their output DAG-CkptSched

◮ In which order should the tasks be executed? ◮ Which tasks should be checkpointed?

We want to minimize the expected execution time.

slide-9
SLIDE 9

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

6

Motivational example

T0 T1 T2 T3 T4 T5 T6 T7

A solution (schedule): Order: T0T1T2T3T4T5T6T7 Ckpted: T1, T4

slide-10
SLIDE 10

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

6

Motivational example

T0 T1 T2 T3 T4 T5 T6 T7 T0 T1 T2 T3 T4

A solution (schedule): Order: T0T1T2T3T4T5T6T7 Ckpted: T1, T4

Time

w0 w1 c1 w2 w3 w4 c4

slide-11
SLIDE 11

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

6

Motivational example

T0 T1 T2 T3 T4 T5 T6 T7

A solution (schedule): Order: T0T1T2T3T4T5T6T7 Ckpted: T1, T4

Time fault

w0 w1 c1 w2 w3 w4 c4

slide-12
SLIDE 12

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

6

Motivational example

T0 T1 T2 T3 T4 T5 T6 T7

A solution (schedule): Order: T0T1T2T3T4T5T6T7 Ckpted: T1, T4

Time

w0 w1 c1 w2 w3 w4 c4

slide-13
SLIDE 13

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

6

Motivational example

T0 T1 T2 T3 T4 T5 T6 T7 T1 T5

A solution (schedule): Order: T0T1T2T3T4T5T6T7 Ckpted: T1, T4

Time

w0 w1 c1 w2 w3 w4 c4 r1 w5

slide-14
SLIDE 14

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

6

Motivational example

T0 T1 T2 T3 T4 T5 T6 T7 T1 T5 T4 T6

A solution (schedule): Order: T0T1T2T3T4T5T6T7 Ckpted: T1, T4

Time

w0 w1 c1 w2 w3 w4 c4 r1 w5 r4 w6

slide-15
SLIDE 15

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

6

Motivational example

T0 T1 T2 T3 T4 T5 T6 T7 T1 T5 T4 T6 T2 T3 T7

A solution (schedule): Order: T0T1T2T3T4T5T6T7 Ckpted: T1, T4

Time

w0 w1 c1 w2 w3 w4 c4 r1 w5 r4 w6 w2 w3 w7

slide-16
SLIDE 16

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

7

Previous results (Bougeret et al. 2011)

Let E[t(w; c; r)] the expected time to execute a single application: w sec. of computation in a fault-free execution c sec. to checkpoint the output r sec. to recover (if a failure occurs) E[t(w; c; r)] = eλr 1 λ + D eλ(w+c) − 1

  • .
slide-17
SLIDE 17

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

8

Theorem

Given a DAG, and a schedule for this DAG, it is possible to compute the expected execution time in polynomial time.

Time

w0 w1 c1 w2 w3 w4 c4 r1 w5 r4 w6 w2 w3 w7

slide-18
SLIDE 18

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

8

Theorem

Given a DAG, and a schedule for this DAG, it is possible to compute the expected execution time in polynomial time. Xi: execution time between the end of the first successful execution of Ti−1 and the end of the first successful execution of Ti (RV).

Time

X0 X1 X5 X7

w0 w1 c1 w2 w3 w4 c4 r1 w5 r4 w6 w2 w3 w7

slide-19
SLIDE 19

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

8

Theorem

Given a DAG, and a schedule for this DAG, it is possible to compute the expected execution time in polynomial time. Xi: execution time between the end of the first successful execution of Ti−1 and the end of the first successful execution of Ti (RV).

Time

X0 X1 X5 X7

w0 w1 c1 w2 w3 w4 c4 r1 w5 r4 w6 w2 w3 w7

We want to compute E[

i Xi] = i E[Xi].

slide-20
SLIDE 20

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

9

Sketch of Proof (1/2)

Z i

k: “There was a fault during Xk and no fault during Xk+1 to Xi−1”

(= when starting Xi, the last fault was during Xk). → E[Xi] =

i−1

  • k=0

P(Z i

k)E[Xi|Z i k]

slide-21
SLIDE 21

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

9

Sketch of Proof (1/2)

Z i

k: “There was a fault during Xk and no fault during Xk+1 to Xi−1”

(= when starting Xi, the last fault was during Xk). → E[Xi] =

i−1

  • k=0

P(Z i

k)E[Xi|Z i k]

T ↓k

i

: all Tj’s whose output should be computed during Xi if Z i

k.

We separate their impact on the execution time into W i

k and Ri k

(depending if Tj was checkpointed).

T0 T2 T3 T4 T6 T7 T1 T5

T4 ∈ T ↓5

6

R6

5 = r4

T1, T5, T2, T3 / ∈ T ↓5

6

Time

w0 w1 c1 w2 w3 w4 c4 r1 w5

slide-22
SLIDE 22

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

9

Sketch of Proof (1/2)

Z i

k: “There was a fault during Xk and no fault during Xk+1 to Xi−1”

(= when starting Xi, the last fault was during Xk). → E[Xi] =

i−1

  • k=0

P(Z i

k)E[Xi|Z i k]

T ↓k

i

: all Tj’s whose output should be computed during Xi if Z i

k.

We separate their impact on the execution time into W i

k and Ri k

(depending if Tj was checkpointed).

T0 T2 T3 T4 T6 T7 T1 T5 T4 T6

T2, T3 ∈ T ↓5

7

W 7

5 = w2 + w3

Time

w0 w1 c1 w2 w3 w4 c4 r1 w5 r4 w6

slide-23
SLIDE 23

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

10

Sketch of Proof (2/2)

E[Xi] = i−1

k=0 P(Z i k)E[Xi|Z i k]

◮ Let i, k s.t. 0 ≤ k < i − 1:

P(Z i

i−1) = 1 − i−2

  • k=0

P(Z i

k)

P(Z i

k) = e−λ i−1

j=k+1(W j k+Rj k+wj+δjcj) · P(Z k+1

k

)

slide-24
SLIDE 24

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

10

Sketch of Proof (2/2)

E[Xi] = i−1

k=0 P(Z i k)E[Xi|Z i k]

Probability of successful execution of Xk+1 to Xi−1 given that there is a fault in Xk. Xj = W j

k + Rj k + wj + δjcj when Z i k

◮ Let i, k s.t. 0 ≤ k < i − 1:

P(Z i

i−1) = 1 − i−2

  • k=0

P(Z i

k)

P(Z i

k) = e−λ i−1

j=k+1(W j k+Rj k+wj+δjcj) · P(Z k+1

k

)

slide-25
SLIDE 25

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

10

Sketch of Proof (2/2)

E[Xi] = i−1

k=0 P(Z i k)E[Xi|Z i k]

Probability that there is a fault in Xk.

◮ Let i, k s.t. 0 ≤ k < i − 1:

P(Z i

i−1) = 1 − i−2

  • k=0

P(Z i

k)

P(Z i

k) = e−λ i−1

j=k+1(W j k+Rj k+wj+δjcj) · P(Z k+1

k

)

slide-26
SLIDE 26

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

10

Sketch of Proof (2/2)

E[Xi] = i−1

k=0 P(Z i k)E[Xi|Z i k]

◮ Let i, k s.t. 0 ≤ k < i − 1:

P(Z i

i−1) = 1 − i−2

  • k=0

P(Z i

k)

P(Z i

k) = e−λ i−1

j=k+1(W j k+Rj k+wj+δjcj) · P(Z k+1

k

)

◮ E[Xi|Z i

k] =

E[t

  • W i

k + Ri k + wi ; δici ; W i i + Ri i −

  • W i

k + Ri k

]

slide-27
SLIDE 27

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

10

Sketch of Proof (2/2)

E[Xi] = i−1

k=0 P(Z i k)E[Xi|Z i k]

By definition of W i

k and Ri k, this is the work to be done after Z i k.

◮ Let i, k s.t. 0 ≤ k < i − 1:

P(Z i

i−1) = 1 − i−2

  • k=0

P(Z i

k)

P(Z i

k) = e−λ i−1

j=k+1(W j k+Rj k+wj+δjcj) · P(Z k+1

k

)

◮ E[Xi|Z i

k] =

E[t

  • W i

k + Ri k + wi ; δici ; W i i + Ri i −

  • W i

k + Ri k

]

slide-28
SLIDE 28

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

10

Sketch of Proof (2/2)

E[Xi] = i−1

k=0 P(Z i k)E[Xi|Z i k]

δi = 0 if Ti is not checkpointed, 1 otherwise

◮ Let i, k s.t. 0 ≤ k < i − 1:

P(Z i

i−1) = 1 − i−2

  • k=0

P(Z i

k)

P(Z i

k) = e−λ i−1

j=k+1(W j k+Rj k+wj+δjcj) · P(Z k+1

k

)

◮ E[Xi|Z i

k] =

E[t

  • W i

k + Ri k + wi ; δici ; W i i + Ri i −

  • W i

k + Ri k

]

slide-29
SLIDE 29

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

10

Sketch of Proof (2/2)

E[Xi] = i−1

k=0 P(Z i k)E[Xi|Z i k]

If there is a failure during Xi, then the work to be done becomes W i

i + Ri i + wi.

◮ Let i, k s.t. 0 ≤ k < i − 1:

P(Z i

i−1) = 1 − i−2

  • k=0

P(Z i

k)

P(Z i

k) = e−λ i−1

j=k+1(W j k+Rj k+wj+δjcj) · P(Z k+1

k

)

◮ E[Xi|Z i

k] =

E[t

  • W i

k + Ri k + wi ; δici ; W i i + Ri i −

  • W i

k + Ri k

]

slide-30
SLIDE 30

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

10

Sketch of Proof (2/2)

E[Xi] = i−1

k=0 P(Z i k)E[Xi|Z i k]

◮ Let i, k s.t. 0 ≤ k < i − 1:

P(Z i

i−1) = 1 − i−2

  • k=0

P(Z i

k)

P(Z i

k) = e−λ i−1

j=k+1(W j k+Rj k+wj+δjcj) · P(Z k+1

k

)

◮ E[Xi|Z i

k] =

E[t

  • W i

k + Ri k + wi ; δici ; W i i + Ri i −

  • W i

k + Ri k

]

◮ LEMMA: We can compute W i

k and Ri k in polynomial time.

slide-31
SLIDE 31

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

11

Other results

Theorem (Complexity)

DAG-CkptSched for fork DAGs can be solved in linear time. DAG-CkptSched for join DAGs is NP-complete.

Theorem

DAG-CkptSched for a join DAG where ci = c and ri = r for all i can be solved in quadratic time.

slide-32
SLIDE 32

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

11

Other results

Theorem (Complexity)

DAG-CkptSched for fork DAGs can be solved in linear time. DAG-CkptSched for join DAGs is NP-complete.

Theorem

DAG-CkptSched for a join DAG where ci = c and ri = r for all i can be solved in quadratic time. Open Problem Complexity of DAG-CkptSched for a general DAG where ci = c and ri = r for all i?

slide-33
SLIDE 33

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

12

Efficient heuristic evaluation

Designing efficient heuristics used to take:

◮ Numerous, time-consuming and expensive stochastic

experiment on an actual platform

◮ Numerous, time-consuming simulations with a

fault-generator Now we can simply compute the expected makespan!

slide-34
SLIDE 34

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

13

2-steps heuristics

Linearization strategies DF Depth First (prio tasks by decreasing outweight) BF Breadth First (prio tasks by decreasing outweight) RF Random First Checkpoint strategies

CkNvr Never checkpoint (default) CkAlws Always checkpoint (default) Below: extensive search for |checkpoint| from 1 to n − 1 CkPer “Periodic” checkpoint CkW Prioritize large wi CkC Prioritize small ci

slide-35
SLIDE 35

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

14

Methodology

We use the Pegasus Workflow Generator to generate realistic synthetic workflows: Montage: mosaics of the sky. Average wi ≈ 10s. Ligo: gravitational waveforms. Average wi ≈ 220s. CyberShake: earthquake hazards. Average wi ≈ 25s. Genome: genome sequence processing. Average wi > 1000s.

◮ We plot the ratio of the expected execution time (T) over the

execution time of a failure-free, checkpoint-free execution (Tinf).

◮ No downtime. ◮ ci = ri = 0.1wi (similar for other values)

slide-36
SLIDE 36

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

15

Results

BF DF RF CkNvr CkAlws CkPer CkW CkC

100 200 300 400 500 600 700 1.08 1.16 1.25 1.33 1.42 1.5

number of tasks T / Tinf

100 200 300 400 500 600 700 1.3 1.35 1.4 1.45 1.5 1.55

number of tasks T / Tinf

Montage: λ = 0.001 Ligo: λ = 0.001

100 200 300 400 500 600 700 1.08 1.14 1.21 1.27 1.34 1.4

number of tasks T / Tinf

100 200 300 400 500 600 700 1.64 1.79 1.94 2.1 2.25 2.4

number of tasks T / Tinf

CyberShake: λ = 0.001 Genome: λ = 0.0001

slide-37
SLIDE 37

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

15

Results

BF DF RF CkNvr CkAlws CkPer CkW CkC

100 200 300 400 500 600 700 1.08 1.16 1.25 1.33 1.42 1.5

number of tasks T / Tinf

100 200 300 400 500 600 700 1.3 1.35 1.4 1.45 1.5 1.55

number of tasks T / Tinf

Montage: λ = 0.001 Ligo: λ = 0.001

100 200 300 400 500 600 700 1.08 1.14 1.21 1.27 1.34 1.4

number of tasks T / Tinf

100 200 300 400 500 600 700 1.64 1.79 1.94 2.1 2.25 2.4

number of tasks T / Tinf

CyberShake: λ = 0.001 Genome: λ = 0.0001

slide-38
SLIDE 38

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

15

Results

BF DF RF CkNvr CkAlws CkPer CkW CkC

100 200 300 400 500 600 700 1.08 1.16 1.25 1.33 1.42 1.5

number of tasks T / Tinf

100 200 300 400 500 600 700 1.3 1.35 1.4 1.45 1.5 1.55

number of tasks T / Tinf

Montage: λ = 0.001 Ligo: λ = 0.001

100 200 300 400 500 600 700 1.08 1.14 1.21 1.27 1.34 1.4

number of tasks T / Tinf

100 200 300 400 500 600 700 1.64 1.79 1.94 2.1 2.25 2.4

number of tasks T / Tinf

CyberShake: λ = 0.001 Genome: λ = 0.0001

slide-39
SLIDE 39

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

15

Results

BF DF RF CkNvr CkAlws CkPer CkW CkC

100 200 300 400 500 600 700 1.08 1.16 1.25 1.33 1.42 1.5

number of tasks T / Tinf

100 200 300 400 500 600 700 1.3 1.35 1.4 1.45 1.5 1.55

number of tasks T / Tinf

Montage: λ = 0.001 Ligo: λ = 0.001

100 200 300 400 500 600 700 1.08 1.14 1.21 1.27 1.34 1.4

number of tasks T / Tinf

100 200 300 400 500 600 700 1.64 1.79 1.94 2.1 2.25 2.4

number of tasks T / Tinf

CyberShake: λ = 0.001 Genome: λ = 0.0001

slide-40
SLIDE 40

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

15

Results

BF DF RF CkNvr CkAlws CkPer CkW CkC

100 200 300 400 500 600 700 1.08 1.16 1.25 1.33 1.42 1.5

number of tasks T / Tinf

100 200 300 400 500 600 700 1.3 1.35 1.4 1.45 1.5 1.55

number of tasks T / Tinf

Montage: λ = 0.001 Ligo: λ = 0.001

100 200 300 400 500 600 700 1.08 1.14 1.21 1.27 1.34 1.4

number of tasks T / Tinf

100 200 300 400 500 600 700 1.64 1.79 1.94 2.1 2.25 2.4

number of tasks T / Tinf

CyberShake: λ = 0.001 Genome: λ = 0.0001

slide-41
SLIDE 41

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

16

◮ BF is not a good heuristic for linearization ◮ CkPer is not a good heuristic for checkpointing DAGs ◮ DF seems to be a good heuristic for linearization ◮ CkW, CkC seem to be good heuristics for checkpointing

(especially CkW)

slide-42
SLIDE 42

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

17

Conclusion

◮ Framework: Applications are scheduled on the whole

platform, subject to IID exponentially distributed failures.

◮ A polynomial time algorithm to compute the expected

makespan for general DAGs.

◮ Polynomial-time algorithm for fork, some join DAGs,

intractability in the general case.

◮ Evaluation of several heuristics on representative workflow

configurations. → Periodic checkpoint is not good for general DAGs.

slide-43
SLIDE 43

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

Future directions

◮ Our key result has opened the capacity of efficient

heuristic design.

◮ On a theoretical point of view:

(i) Non-blocking checkpoint (ii) Remove linearization assumption

slide-44
SLIDE 44

Workflow scheduling with failures

  • G. Aupy

Motivation Models

Platform Fault-tolerance Application

Results

Exp’d makespan Other

Heuristic evaluation

Heuristics Evaluation

Conclusion

Future directions

◮ Our key result has opened the capacity of efficient

heuristic design.

◮ On a theoretical point of view:

(i) Non-blocking checkpoint (ii) Remove linearization assumption

Thanks