Operational Experiences with Disk Imaging in a Multi-Tenant - - PowerPoint PPT Presentation

operational experiences with disk imaging in a multi
SMART_READER_LITE
LIVE PREVIEW

Operational Experiences with Disk Imaging in a Multi-Tenant - - PowerPoint PPT Presentation

Operational Experiences with Disk Imaging in a Multi-Tenant Datacenter Kevin Atkinson, Gary Wong, and Robert Ricci 2 2 2 2 2 2 2 Properties of disk images and their usage have consequences for: Storage


slide-1
SLIDE 1

Operational Experiences with Disk Imaging in a Multi-Tenant Datacenter

Kevin Atkinson, Gary Wong, and Robert Ricci

slide-2
SLIDE 2

2

slide-3
SLIDE 3

2

slide-4
SLIDE 4

2

slide-5
SLIDE 5

2

slide-6
SLIDE 6

2

slide-7
SLIDE 7

2

slide-8
SLIDE 8

2

slide-9
SLIDE 9

3

Properties of disk images and their usage have consequences for:

  • ❖ Storage

❖ Caching ❖ Pre-loading ❖ Distribution

slide-10
SLIDE 10

4

slide-11
SLIDE 11

4

What does the working set look like?

slide-12
SLIDE 12

4

What does the working set look like? What do the images themselves look like?

slide-13
SLIDE 13

4

What does the working set look like? What do the images themselves look like? What are the key factors in pre-loading?

slide-14
SLIDE 14

The dataset

❖ Four years (2009-2013): 279,972 requests ❖ Users: 1,301 individuals, 368 organizations ❖ Unique images: 714 ❖ Emulab ❖ ~600 PCs ❖ Facility / user image model

5

slide-15
SLIDE 15

User Behavior

slide-16
SLIDE 16

“Emulab is a pretty odd beast and its users are even weirder.”

7

slide-17
SLIDE 17

–Reviewer D

“Emulab is a pretty odd beast and its users are even weirder.”

7

slide-18
SLIDE 18

–Reviewer D [Emulab user]

“Emulab is a pretty odd beast and its users are even weirder.”

7

slide-19
SLIDE 19

Facility vs. user images

8

Facility User 55.6% 44.4%

slide-20
SLIDE 20

Facility vs. user images

8

Facility User 55.6% 44.4%

slide-21
SLIDE 21

Facility vs. user images

8

Facility User 55.6% 44.4%

  • 1) Most users stick to facility or user images

2) Heaviest users use their own images

slide-22
SLIDE 22

Image popularity

9

slide-23
SLIDE 23

Image popularity

9

slide-24
SLIDE 24

Image popularity

9

slide-25
SLIDE 25

Image popularity

9

slide-26
SLIDE 26

Image popularity

9

Exponential

slide-27
SLIDE 27

Image popularity

9

Exponential Heavy-Tailed

slide-28
SLIDE 28

Image popularity

9

1) Facility images have a smaller, lighter tail 2) Most popular image < 13% of requests

Exponential Heavy-Tailed

slide-29
SLIDE 29

Scaling: total images

10

slide-30
SLIDE 30

Scaling: total images

10

slide-31
SLIDE 31

Scaling: total images

10

slide-32
SLIDE 32

Scaling: total images

10

As userbase grows, user images dominate the totals

slide-33
SLIDE 33

Daily working set

11

slide-34
SLIDE 34

Daily working set

11

Small image set each day –※ good caching potential

slide-35
SLIDE 35

Scaling: working set

12

slide-36
SLIDE 36

Scaling: working set

12

slide-37
SLIDE 37

Scaling: working set

12

slide-38
SLIDE 38

Scaling: working set

12

Facility will max out

slide-39
SLIDE 39

Scaling: working set

12

Facility will max out –※ In the limit, highly popular facility images account for most requests

slide-40
SLIDE 40

Image Contents

slide-41
SLIDE 41

Block-level similarity

14

Base

slide-42
SLIDE 42

Block-level similarity

14

Base Derived

slide-43
SLIDE 43

Block-level similarity

14

Base Derived

slide-44
SLIDE 44

Block-level similarity

14

Percentage of blocks that need to be written to transform the base image into derived

Base Derived

slide-45
SLIDE 45

Block-level similarity

15

Derived: User image Base: Most similar facility image

slide-46
SLIDE 46

Block-level similarity

15

Derived: User image Base: Most similar facility image

slide-47
SLIDE 47

Block-level similarity

15

Derived: User image Base: Most similar facility image 1) De-duplicating storage an attractive option 2) Differential loading has potential

slide-48
SLIDE 48

Pre-Loading

slide-49
SLIDE 49

Pre-loading: Size

17

slide-50
SLIDE 50

Pre-loading: Size

17

Spare Capacity

slide-51
SLIDE 51

Pre-loading: Size

17

Spare Capacity Mostly Full

slide-52
SLIDE 52

Pre-loading: Size

17

Spare Capacity Mostly Full

WSS for facility images maxes out

  • n large facilities
slide-53
SLIDE 53

Pre-loading: Size

17

Spare Capacity Mostly Full

1) Key: Ratio of WSS to idle capacity 2) Effective when ratio is high WSS for facility images maxes out

  • n large facilities
slide-54
SLIDE 54

Pre-loading: Rate

18

slide-55
SLIDE 55

Pre-loading: Rate

18

slide-56
SLIDE 56

Pre-loading: Rate

18

Invest in fast, scalable imaging

slide-57
SLIDE 57

Conclusions

slide-58
SLIDE 58

General conclusions

❖ Deduplicating, two-tier storage attractive ❖ Caching can be effective ❖ Image lifespan, idle periods ❖ Treat facility and user images differently ❖ Facility better targets for pre-loading ❖ Differential loading requires new strategies ❖ Potential savings, outline of optimization problem ❖ Images per organization, WSS per week

20

slide-59
SLIDE 59

21

Explore the data, reproduce our results:

  • http://aptlab.net/p/tbres/nsdi14
slide-60
SLIDE 60
  • No dominant images

22

slide-61
SLIDE 61
  • No dominant images

22

No image dominates long-term, popular images change frequently

slide-62
SLIDE 62

Image lifespan

23

slide-63
SLIDE 63

Image lifespan

23

A few days

slide-64
SLIDE 64

Image lifespan

23

A few days Four Years

slide-65
SLIDE 65

Image lifespan

23

A few days Four Years

Two-tiered storage system attractive

slide-66
SLIDE 66

Savings from deltas

24

slide-67
SLIDE 67

Images per organization

25

slide-68
SLIDE 68

Idle images

26

slide-69
SLIDE 69

WSS per week

27

slide-70
SLIDE 70

Top images

28 RHL90-STD [D] 21,993 7.9% FEDORA10-STD 18,042 6.4% UBUNTU10-STD 14,402 5.1% RHL90-STD 13,182 4.7% FC4-UPDATE 12,097 4.3%

u

715/10 11,156 4.0% FBSD410-STD 8,916 3.2% FEDORA8-STD 8,153 2.9%

u

237/69 7,512 2.7%

u

296/35 7,179 2.6%

u

787/24 6,243 2.2% UBUNTU70-STD 6,021 2.2% UBUNTU12-64-STD 5,834 2.1%

slide-71
SLIDE 71

Size considerations

❖ Small facilities with few idle disks ❖ Pre-loading not valuable ❖ Large facilities - focus on: ❖ Scalable reloading mechanisms ❖ Prediction and optimization for user requests

29