I made a map of the internet and other lessons about speeding up web sites

TH
by Tom Hughes-Croucher6 views·Updated Jun 22, 2010
Powered by AI

Need to present on this topic?

Create your own polished presentation in minutes. Just describe what you need.

Free to try, no credit card required

Transcript

Tom Hughes-Croucher

Yahoo! Inc.

@sh1mmer

P.S.

Some of this might be wrong

Work in progress

"Remember Routers Switch and Switches Route"

Physics

TCP

Wifi

I made a map of the Internet

From here

To Here

Basics

Backbone

1, 6 and 11 are most popular in the USA because they don't overlap

Real Example

Thanks to EventHelix.com

HTTP

OFCOM Study

  • 90% of bandwidth on management

Sources of interference:

  • Microwaves
  • Cordless Phones
  • Baby Monitors
  • etc

Fiber Optics

at the <3 of everything

The 500 Mile Email

Issues/Solutions

http://www.ibiblio.org/harris/500mailemail.html

Issues/Solutions

Mother Earth Mother Board

  • Wifi connectivity - FCC need to find a solution to the congested airspace
  • Modems - ISPs need to stop shipping shitty gear
  • Speed of light - Um, yeah
  • Bandwidth - More fiber to the home, etc

Basics

http://www.wired.com/wired/archive/4.12/ffglass_pr.html

  • Tear-up/down - SPDY

- Cheap-alive

  • Framesize - Use aggressive settings
  • Slow-start - Use agressive settings

- Watch out for routers

  • Pescribed routing - MPTCP

Issues/Solutions

IP

METHODS

  • GET
  • HEAD
  • OPTIONS
  • PUT
  • POST
  • DELETE
  • Multiple request - SPDY

- HTTP Pipeline

  • Caching - CDNs
  • Latency - Parellising requests

2xx - OK

3xx - Redirect

4xx - Client Error

5xx - Server Error

RESPONSES

Routing

Issues/Solutions

Classic Waterfall Chart

And other lessons

about speeding

up web sites

Does Cache Matter?

Latency vs. Bandwidth

A

1. Send to 128.9.2.2

2. 128.9.0.0 Matched to 128.8.1.1

3. 128.8.1.1 Matched to LAN 0

4. Construct Packet

5. ARP -> MAC

6. Send

1. Recieve Packet

2. 128.9.2.0 Matched to LAN 2

3. Construct Packet

4. ARP -> MAC

5. Send

C

1. Recieve Packet

2. Matched self

3. Read Packet

By Mike Belshee

UDP

"Fire and forget"

TCP

UDP

Rendering

Issues/Solutions

DNS

Browsers

  • Network
  • Parse
  • Render
  • Paint
  • Scripts

Anycast

Issues/Solutions

Geo-DNS

Issues/Solutions

CNAME recursion

  • Geography - Anycast

- Geo Fixing

  • Lookup recursion - Use nested CNAME records
  • Bad DNS - OpenDNS/Google DNS
  • Lookup times - Reduce DNS requests

Initial paint - Flush, flush, flush

Reflow - Check CSS

Repaint - Check JavaScript

Render time - decision trees

Non-blocking loading - LabJS

Tools & Research

Rendering

HTTP

TCP/IP

DNS

Tools

Research

Tools

Research

Tools

Research

Tools

Research

  • Dynatrace
  • Speed Tracer
  • Wireshark
  • tcpdump
  • Early Flushing
  • JavaScript styling
  • MHTML
  • SPDY
  • Slow Start
  • MPTCP
  • HTTP Pipelines
  • SPDY
  • Wireshark
  • Firebug
  • Web Inspector
  • Dynatrace
  • OpenDNS
  • Google DNS
  • Geo DNS
  • Prefetching
  • dig
  • whois
  • Wireshark
  • tcpdump

Basics

YSlow - http://developer.yahoo.com/yslow

Firebug - http://getfirebug.com

Page Speed - http://code.google.com/speed/page-speed

Dynatrace - http://dynatrace.com

Speed Tracer - http://code.google.com/webtoolkit/speedtracer

Wireshark - http://wireshark.org

Tom Hughes-Croucher

Yahoo! Inc.

http://developer.yahoo.com/performance

http://speakerrate.com/sh1mmer

@sh1mmer

croucher@yahoo-inc.com