Slide 1

Slide 1 text

YAY? SPDY? @marthakelly

Slide 2

Slide 2 text

WAT is SPDY? Networking Protocol Session layer on top of HTTP Transports web content Reduces latency

Slide 3

Slide 3 text

LMAO HTTP! HTTP was proposed in 1991 Single request per connection FIFO queues Only client initiated requests Uncompressed headers Redundant Headers

Slide 4

Slide 4 text

OMG HEADERS! Request headers can be 2KB (cookies, user agents expand features) HTTP sends redundant headers Host User Agent Accept* headers are static

Slide 5

Slide 5 text

SO MUCH HAS CHANGED SINCE 1991

Slide 6

Slide 6 text

How does SPDY work? It works “on top” of HTTP/TCP SPDY is delivered via SSL Introduces new framing layer Reduces latency with Compression Multiplexing Prioritization

Slide 7

Slide 7 text

SPDY sauce Multiple (unlimited) simultaneously multiplexed requests over a single TCP connection Fewer, but more densely packed packets are issued Connection is bi-directional, servers can push data to clients Server Hints

Slide 8

Slide 8 text

MEH, CAVEATS SPDY only works per domain It doesn't prevent scripts from blocking other resources SSL latency penalty

Slide 9

Slide 9 text

YAY!!1 SPDY! Domain sharding could now be obsolete More wide usage of SSL increases security for everyone Packet loss penalty reduced 48% speedup at 2% (IRL packet loss rates are typically 1-2%) TCP++

Slide 10

Slide 10 text

THX SPDY! (& THX EVERYONE) @marthakelly