Slide 1

Slide 1 text

You Ain't SPDY Chris Strom (@eee_c) GoGaRuCo 2011-09-16

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

@spdybook @backbonerecipes w/ Nick Gauthier

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

SPDY is a replacement for HTTP

Slide 7

Slide 7 text

SPDY is backwards compatible with HTTP

Slide 8

Slide 8 text

SPDY still does HTTP-like things

Slide 9

Slide 9 text

SPDY is optimized for page load times

Slide 10

Slide 10 text

A Tale of Two Websites by httparchive.org

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

38% of broadband users will close a site if it doesn't respond in 4 seconds

Slide 21

Slide 21 text

38% of broadband users will close a site if it doesn't respond in 4 seconds (precision is the key to any good statistic)

Slide 22

Slide 22 text

= $$$

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

That's freaking crazy

Slide 26

Slide 26 text

Site #2...

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

took 4.2 seconds to load 469kB of data over 75 requests

Slide 32

Slide 32 text

took 4.2 seconds to load 469kB of data over 75 requests took ??? seconds to load 806kB of data over 83 requests

Slide 33

Slide 33 text

took 4.2 seconds to load 469kB of data over 75 requests took ??? seconds to load 806kB of data over 83 requests Average: 816kB of data over 83 requests

Slide 34

Slide 34 text

How does Amazon do it?

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

But wait! There's more...

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

Got all that?

Slide 63

Slide 63 text

HTTP Optimizations

Slide 64

Slide 64 text

!HTTP Optimizations

Slide 65

Slide 65 text

!HTTP Optimizations HTTP Workarounds

Slide 66

Slide 66 text

HTTP is antiquated

Slide 67

Slide 67 text

HTTP is antiquated HTTP has not been updated in 12 years

Slide 68

Slide 68 text

HTTP is antiquated HTTP has not been updated in 12 years HTTP is old

Slide 69

Slide 69 text

HTTP is antiquated HTTP has not been updated in 12 years HTTP is old HTTP is so old...

Slide 70

Slide 70 text

No content

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

SPDY!

Slide 78

Slide 78 text

SPDY! It offers no new ideas!

Slide 79

Slide 79 text

+

Slide 80

Slide 80 text

Bandwidth Will Save US!

Slide 81

Slide 81 text

Bandwidth Will Save US! (won't it?)

Slide 82

Slide 82 text

Bandwidth Doesn't Matter

Slide 83

Slide 83 text

Bandwidth Doesn't Matter Beyond ~3mpbs, it make no difference on page load.

Slide 84

Slide 84 text

Bandwidth is for Downloading Ubuntu (not the Ubuntu download page)

Slide 85

Slide 85 text

SPDY is About Page Load Time It has other benefits, but its main goal is to decrease page load time

Slide 86

Slide 86 text

The Internet is built of tubes...

Slide 87

Slide 87 text

Data travels One Way thru HTTP Tubes (kinda like a stargate)

Slide 88

Slide 88 text

HTTP Tubes in Action

Slide 89

Slide 89 text

No content

Slide 90

Slide 90 text

Problem Solved

Slide 91

Slide 91 text

Problem Solved ?

Slide 92

Slide 92 text

Brrr..! Connections Need to be Warmed thermometer indicating cold temperature

Slide 93

Slide 93 text

Warm Connections == Higher Bandwidth

Slide 94

Slide 94 text

No content

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

No content

Slide 97

Slide 97 text

No content

Slide 98

Slide 98 text

No content

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

Why Not Start the Tubes Warm? ● Large congestion window (CWND) ● CWND is initially 3 ● 6 connections => we already have 18 initial CWND

Slide 101

Slide 101 text

Why Not Start the Tubes Warm? ● Large congestion window (CWND) ● CWND is initially 3 ● 6 connections => we already have 18 initial CWND ● Already subverting TCP/IP ● Is subverting further a good idea? ● Especially given data loss rates that we already see?

Slide 102

Slide 102 text

SPDY Tube...!

Slide 103

Slide 103 text

SPDY Conversations...!

Slide 104

Slide 104 text

SPDY ● Built on SSL ● Binary ● Don't send redundant header information ● Aggressively compress stuff ● Use a single(!) tube ○ Only pay the warm-up penalty once ○ Just like downloading an Ubuntu ISO!!!

Slide 105

Slide 105 text

SPDY ● SYN_STREAM ● SYN_REPLY ● RST_STREAM ● SETTINGS ● HEADERS ● PING ● GOAWAY ● WINDOW_UPDATE ● DATA

Slide 106

Slide 106 text

Current State of SPDY in Ruby In a word....

Slide 107

Slide 107 text

Current State of SPDY in Ruby In a word.... Ugh.

Slide 108

Slide 108 text

● An openssl-generated server key ● The SPDY Gem ● Edge-openssl for NPN (Next Protocol Negotiation) ● Carson McDonald's NPN enabled fork of eventmachine* (in the tls-npn branch) — pull request #196 * https://github.com/carsonmcdonald/eventmachine

Slide 109

Slide 109 text

No content

Slide 110

Slide 110 text

No content

Slide 111

Slide 111 text

No content

Slide 112

Slide 112 text

No content

Slide 113

Slide 113 text

No content

Slide 114

Slide 114 text

https://github.com/igrigorik/spdy/issues/2

Slide 115

Slide 115 text

If browsers had a single connection...

Slide 116

Slide 116 text

Closer to Real Browser Connections

Slide 117

Slide 117 text

Packaging/Compressing Responses

Slide 118

Slide 118 text

SPDY Server Push

Slide 119

Slide 119 text

SPDY Server Push Pushes data directly into the browser cache

Slide 120

Slide 120 text

Client Request (SYN_STREAM) +----------------------------------+ 80 02 00 01 |1| Version | 1 | +----------------------------------+ 02 00 00 38 | Flags (8) | Length (24 bits) | +----------------------------------+ 00 00 00 01 |X| Stream-ID (31bits) | +----------------------------------+ 00 00 00 00 |X|Associated-To-Stream-ID (31bits)| +----------------------------------+ 00 00 62 60 | Pri | Unused | | +------------------ | 64 60 06 05 | Name/value header block | 81 42 46 49 | ... | 49 41 b1 95 ....

Slide 121

Slide 121 text

Server Response (SYN_REPLY) +----------------------------------+ 80 02 00 02 |1| Version | 2 | +----------------------------------+ 00 00 00 a4 | Flags (8) | Length (24 bits) | +----------------------------------+ 00 00 00 01 |X| Stream-ID (31bits) | +----------------------------------+ 00 00 78 bb | Unused | | df a2 51 b2 +---------------- | 62 e0 64 e0 | Name/value header block | 42 c4 10 03 | ... | 57 76 6a 6a

Slide 122

Slide 122 text

Server Push (SYN_STREAM) +----------------------------------+ 80 02 00 01 |1| Version | 1 | +----------------------------------+ 02 00 00 51 | Flags (8) | Length (24 bits) | +----------------------------------+ 00 00 00 02 |X| Stream-ID (31bits) | +----------------------------------+ 00 00 00 01 |X|Associated-To-Stream-ID (31bits)| +----------------------------------+ 00 00 62 60 | Pri | Unused | | +------------------ | | Name/value header block | 23 c2 37 cc | ... | a0 40 52 c8 28 29 29 28

Slide 123

Slide 123 text

SPDY Server Push

Slide 124

Slide 124 text

SPDY Server Push

Slide 125

Slide 125 text

SPDY Server Push

Slide 126

Slide 126 text

SPDY Server Push

Slide 127

Slide 127 text

SPDY Server Push

Slide 128

Slide 128 text

Server Push #2 (SYN_STREAM) +----------------------------------+ 80 02 00 01 |1| Version | 1 | +----------------------------------+ 02 00 01 5b | Flags (8) | Length (24 bits) | +----------------------------------+ 00 00 00 04 |X| Stream-ID (31bits) | +----------------------------------+ 00 00 00 01 |X|Associated-To-Stream-ID (31bits)| +----------------------------------+ 00 00 62 60 | Pri | Unused | | +------------------ | | Name/value header block | 23 c2 37 cc | ... | a0 40 52 c8 28 29 29 28

Slide 129

Slide 129 text

SPDY Server Push

Slide 130

Slide 130 text

SPDY Server Push

Slide 131

Slide 131 text

SPDY Server Push

Slide 132

Slide 132 text

SPDY Server Push

Slide 133

Slide 133 text

SPDY Server Push

Slide 134

Slide 134 text

No content

Slide 135

Slide 135 text

No content

Slide 136

Slide 136 text

No content

Slide 137

Slide 137 text

No content

Slide 138

Slide 138 text

No content

Slide 139

Slide 139 text

No content

Slide 140

Slide 140 text

No content

Slide 141

Slide 141 text

No content

Slide 142

Slide 142 text

took 11.4 seconds to load 806kB of data over 83 requests

Slide 143

Slide 143 text

Thanks! Chris Strom (@eee_c) spdybook.com Coupon: gogaruco2011 (free!) Coming soon! Recipes with Backbone(.js) recipeswithbackbone.com