Efficient Distributed Workload (Re-)Embedding Monika Stefan - - PowerPoint PPT Presentation

efficient distributed workload re embedding
SMART_READER_LITE
LIVE PREVIEW

Efficient Distributed Workload (Re-)Embedding Monika Stefan - - PowerPoint PPT Presentation

Efficient Distributed Workload (Re-)Embedding Monika Stefan Stefan Henzinger Neumann Schmid Many Years Ago Single server Systems were fixed and workload-agnostic Simple communication patterns (if at all), endpoints fixed


slide-1
SLIDE 1

Efficient Distributed Workload (Re-)Embedding

Stefan Neumann Monika Henzinger Stefan Schmid

slide-2
SLIDE 2

Many Years Ago

  • Single server
  • Systems were fixed and

workload-agnostic

  • Simple communication

patterns (if at all),
 endpoints fixed

https://www.flickr.com/photos/jurvetson/157722937

2

slide-3
SLIDE 3

Nowadays

  • Large distributed systems


(even geographically distributed):

communication over network

  • Virtualization technologies

enable workload-aware

  • perations that improve system

efficiency

  • Communicating processes can

be far away and
 re-locating them is costly

https://wikileaks.org/amazon-atlas/map/
 https://commons.wikimedia.org/wiki/File:Bacloud.com_data_center.JPG

3

slide-4
SLIDE 4

Nowadays

  • Large distributed systems


(even geographically distributed):

communication over network

  • Virtualization technologies

enable workload-aware

  • perations that improve system

efficiency

  • Communicating processes can

be far away and
 re-locating them is costly

  • Communication requests

contain patterns

https://wikileaks.org/amazon-atlas/map/
 https://commons.wikimedia.org/wiki/File:Bacloud.com_data_center.JPG

3

slide-5
SLIDE 5

Nowadays

  • Large distributed systems


(even geographically distributed):

communication over network

  • Virtualization technologies

enable workload-aware

  • perations that improve system

efficiency

  • Communicating processes can

be far away and
 re-locating them is costly

  • Communication requests

contain patterns

https://wikileaks.org/amazon-atlas/map/
 https://commons.wikimedia.org/wiki/File:Bacloud.com_data_center.JPG


 
 
 


How to exploit the patterns? When to
 re-locate workloads?

New challenge

3

slide-6
SLIDE 6

The Model

4

slide-7
SLIDE 7

The Model

ℓ servers

4

slide-8
SLIDE 8

The Model

ℓ servers

4

data centers RACK scale computing

slide-9
SLIDE 9

The Model

server

ℓ servers

4

data centers RACK scale computing

slide-10
SLIDE 10

The Model

server

  • ccupied

VM slot

n

n virtual machines (VMs)

The VMs are the workloads.

5

slide-11
SLIDE 11

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

εn additional slots for VMs

6

slide-12
SLIDE 12

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

7

slide-13
SLIDE 13

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

7

slide-14
SLIDE 14

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

7

slide-15
SLIDE 15

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

7

slide-16
SLIDE 16

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

7

slide-17
SLIDE 17

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Old communication links stay forever

8

slide-18
SLIDE 18

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

9

slide-19
SLIDE 19

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

1

9

slide-20
SLIDE 20

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

1 1

9

slide-21
SLIDE 21

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Communication requests arrive online

1 1 1

9

slide-22
SLIDE 22

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α > 1

re-location cost

10

slide-23
SLIDE 23

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α

α > 1

re-location cost

11

slide-24
SLIDE 24

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α

α > 1

re-location cost

12

slide-25
SLIDE 25

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α > 1

re-location cost

13

slide-26
SLIDE 26

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α

α > 1

re-location cost

14

slide-27
SLIDE 27

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α

α > 1

re-location cost

15

slide-28
SLIDE 28

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α > 1

re-location cost

16

slide-29
SLIDE 29

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α

α > 1

re-location cost

17

slide-30
SLIDE 30

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α

α > 1

re-location cost

18

slide-31
SLIDE 31

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

Re-locate VMs to avoid cross-server communication

α > 1

re-location cost

19

slide-32
SLIDE 32

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

  • Internal server communication cost:
  • Server-server communication cost:

1

  • VM re-location cost:

➡ Given an online sequence of communication requests,


minimize total cost paid for communication

α

1

α

20

slide-33
SLIDE 33

The Model

server

  • ccupied

VM slot free
 VM slot

n εn

  • Internal server communication cost:
  • Server-server communication cost:

1

  • VM re-location cost:

➡ Given an online sequence of communication requests,


minimize total cost paid for communication

α

20

After all communications finished: 1 server = 1 component

slide-34
SLIDE 34

Analysis

  • Competitive analysis comparing to OPT:
  • OPT knows all communications in advance
  • OPT computes solution with optimal cost
  • (Strict) competitive ratio =

server

  • ccupied

VM slot free
 VM slot

n εn

ALG OPT

21

slide-35
SLIDE 35

Results

  • For servers:
  • Algorithm which is -competitive
  • Lower bound: Any algorithm must be

  • competitive

➡ Our results are almost tight for two servers

server

  • ccupied

VM slot free
 VM slot

2

n εn

O ( log n ε )

Ω(1/ε + log n)

22

ℓ = 2

slide-36
SLIDE 36

Results

  • For servers:
  • Algorithm which is -competitive

➡ Efficient when is small,


e.g., for communication across data centers

➡ Implementable for distributed computation


communication cost ≤ communication for re-locating VMs

server

  • ccupied

VM slot free
 VM slot

n εn

O ((ℓ log n log ℓ)/ε)

ℓ ℓ

ℓ = O ( εn)

(if )

23

slide-37
SLIDE 37

Applications

  • Distributed Union Find Data Structure


(with small cost for re-locating the sets across servers)

  • Online Balanced k-way Partition


(with small cost for re-assigning numbers to balanced partitions)

24

slide-38
SLIDE 38

Algorithm for Two Servers

Color each VM based on its initial server

25

slide-39
SLIDE 39

Algorithm for Two Servers

26

slide-40
SLIDE 40

Algorithm for Two Servers

26

slide-41
SLIDE 41

Algorithm for Two Servers

Move small component to larger one

26

slide-42
SLIDE 42

Algorithm for Two Servers

Move small component to larger one

26

slide-43
SLIDE 43

Algorithm for Two Servers

Move small component to larger one

27

slide-44
SLIDE 44

Algorithm for Two Servers

Move small component to larger one

28

slide-45
SLIDE 45

Algorithm for Two Servers

Move small component to larger one

28

slide-46
SLIDE 46

Algorithm for Two Servers

Move small component to larger one

28

slide-47
SLIDE 47

Algorithm for Two Servers

Move small component to larger one

29

slide-48
SLIDE 48

Algorithm for Two Servers

Move small component to larger one

30

slide-49
SLIDE 49

Algorithm for Two Servers

30

slide-50
SLIDE 50

Algorithm for Two Servers

31

slide-51
SLIDE 51

Algorithm for Two Servers

Contains more yellow than green VMs

31

slide-52
SLIDE 52

Algorithm for Two Servers

Majority-voting step

Contains more yellow than green VMs

31

slide-53
SLIDE 53

Algorithm for Two Servers

Majority-voting step

Contains more yellow than green VMs assign to yellow server

31

slide-54
SLIDE 54

Algorithm for Two Servers

Majority-voting step

Contains more yellow than green VMs assign to yellow server

32

slide-55
SLIDE 55

Algorithm for Two Servers

Majority-voting step

Contains more yellow than green VMs assign to yellow server

Ensures that we stay close to initial assignment

32

slide-56
SLIDE 56

For each new
 communication request:

  • Move smaller component to the


server of the larger one


  • If size of new component exceeds

a power of 2:
 Perform majority-voting step


  • If server capacity exceeded:


Find cheapest balanced
 assignment using
 brute-force enumeration

Can only happen
 times

O ( log n ε )

33

slide-57
SLIDE 57

Generalization to Servers

S0 S1 S2 S3 S4 S5 S6 S7

34

slide-58
SLIDE 58

Generalization to Servers

S0 S1 S2 S3 S4 S5 S6 S7

34

slide-59
SLIDE 59

Generalization to Servers

S0 S1 S2 S3 S4 S5 S6 S7

34

slide-60
SLIDE 60

Generalization to Servers

S0 S1 S2 S3 S4 S5 S6 S7

Traverse tree from root downwards and
 perform majority voting step at each internal node

34

slide-61
SLIDE 61

Generalization to Servers

S0 S1 S2 S3 S4 S5 S6 S7

Traverse tree from root downwards and
 perform majority voting step at each internal node

34

slide-62
SLIDE 62

Generalization to Servers

S0 S1 S2 S3 S4 S5 S6 S7

Traverse tree from root downwards and
 perform majority voting step at each internal node

34

slide-63
SLIDE 63

Generalization to Servers

S0 S1 S2 S3 S4 S5 S6 S7

Traverse tree from root downwards and
 perform majority voting step at each internal node

34

slide-64
SLIDE 64

Summary

  • We introduced a new model for
  • nline workload (re-)embedding
  • Distributed algorithm which is

  • competitive
  • Applications to version of

fundamental problems such as union find and k-way partition O ((ℓ log n log ℓ)/ε)

35

S0 S1 S2 S3 S4 S5 S6 S7

slide-65
SLIDE 65

Open Problems

  • Our algorithm for servers has competitive-ratio


. Can we shave the -factor?

  • Study generalized setting where communication patterns

can change arbitrarily over time

  • Tuning our algorithms further to perform even better in

specific use cases

O ((ℓ log n log ℓ)/ε)

ℓ ℓ

36

slide-66
SLIDE 66

Efficient Distributed Workload (Re-)Embedding

Distributed
 Union Find Data Structure


(with small cost
 for re-locating the sets)

Online
 Balanced k-way Partition


(with small cost
 for assigning numbers to partitions)

Applications

37

new model for distributed workload (re-)embedding

Thank you!

O ((ℓ log n log ℓ)/ε)

distributed algorithm with competitive ratio

slide-67
SLIDE 67

Related Work

  • Avin et al. (DISC’16, SIDMA’19):
  • No ground-truth assumption
  • -competitive algorithm
  • Competitive ratio for deterministic algorithms is


38

Ω(n/ℓ) ˜ O(n/ℓ)