Optimizing Web Performance by         Using Fast DNSTom DalyChief Scientist, Dyn Labstom@dyn.com | @tomdyninc#velocityconf...
Goal of the Talk   • Understand the impact of DNS response latency on     total web page load time   • Understand the trad...
Connecting DNS and HTTP Load Time   • Speed metrics:           – Google: 400ms => 0.6% search decrease           – Shopzil...
Understand the Tradeoffs   • HTTP optimizations everywhere! Yslow, ShowSlow,     etc.   • Many HTTP optimizations ignore D...
A Worst Case Scenario!  Poor anycast + CDN CNAME chain + back to origin nodeOptimizing Web Performance By Using Fast DNS  ...
Don’t worry, there is hope!Optimizing Web Performance By Using Fast DNS                                                  D...
Easy Wins for WebOps   • Higher TTLs mean less queries to keep cache hot, less     agility in moving resources around     ...
Harder Wins for WebOps   • Offline nameservers / Lame delegations           – This means timed out queries upstream: 2 or ...
Hardest Win for WebOps   • Self Deploy a Proper DNS Architecture:           – For speed and performance, you must deploy a...
Traditional DNS: Unicast   • Need to deploy many nameservers for redundancy     and geographic diversity.   • With Unicast...
Today’s DNS: Anycast   • Again, need to deploy many nameservers for     redundancy and geographic diversity.   • But with ...
The Ultimate Performance Enemy:                     DNS Protocol Resiliency   • When was the last time you saw a DNS query...
Unicast Experience   ns1: Seattle                                         ns4: New York ns2: Palo Alto                    ...
Anycast Experience   ns1: Seattle                                        ns1: New York ns2: Palo Alto                     ...
Handling Site Outages   • What happens during an Unicast site outage?           – RTT banding timeouts delay DNS query res...
Unicast Redundancy   ns1: Seattle                                       ns4: New York ns2: Palo Alto                      ...
Anycast Redundancy   ns1: Seattle                                      ns1: New York ns2: Palo Alto                       ...
Handling DDoS   • What happens during an Unicast DDoS?           – Likely, all of the nameservers in the delegation will b...
Unicast DDoS   ns1: Seattle                                         ns4: New York ns2: Palo Alto                          ...
Anycast DDoS   ns1: Seattle                                         ns1: New York ns2: Palo Alto                          ...
Anycast sounds pretty                          awesome, right?Optimizing Web Performance By Using Fast DNS                ...
Deploying Anycast Services   • Deploying anycast isn’t easy:           – Understanding / capability of BGP routing        ...
Routing 101   • Backbones and routing protocols:           – IGP (OSPF) for internal connections (link state / metric base...
Internet Scale Routing                                                AS 2          AS 3                                AS...
BGP 101   • With BGP, routing information is exchanged between     “peers” – routers connected to each other   • Only the ...
BGP Routing                                                AS 2          AS 3                                AS 1         ...
BGP Routing Example   tom@core-01-ewr.dyndns.com> show route www.level3.com   inet.0: 409151 destinations, 1656770 routes ...
OSPF + iBGP 101   • IGP (OSPF) enumerates all potential “paths” and     “costs” in the network.   • Links between routers ...
OSPF Routing in AS4                                                AS 2          AS 3                                AS 1 ...
IGP (iBGP + OSPF) Routing    inet.0: 414878 destinations, 4526985 routes (413866 active, 19 holddown, 422693 hidden)    20...
Anycast, BGP and OSPF   • To make Anycast work, you need to:           – Understand the impact of BGP peering upon route p...
Putting it All Together                                               AS 2          AS 3                               AS ...
Aut. Systems and IP Addresses   • To multihome your network, you need to run BGP;     you need an autonomous system number...
Datacenters, IP Transit, and Peering   • Consistent ISP connectivity is key to ensure networks     take advantage of IGP m...
Data Synchronization and Monitoring   • Two networks are deployed:           – First for Anycast services facing TOWARDs u...
Example Datacenter Configuration                        ISP #1                 ISP #2BGP Announcement:208.78.69.0/24208.78...
Example BGP Peer Config   show configuration protocols bgp   ...   group NTT {       type external;       peer-as 2914;   ...
Example Routing Policy Config   show configuration policy options   ...   policy-statement Dyn-Anycast {       term advert...
Example Static Route Config   show configuration routing-options   ...   static {       route 0.0.0.0/0 next-hop 129.250.1...
Example Server Config   [tom@dns ~]$ ifconfig igb0   igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu...
Do this Twice and…Anycast                    And it works for HTTP services too!                        ISP #1            ...
Example Improvements   • Warning: YMMV! But let’s chat about it.   • Monitoring from 50 Catchpoint Nodes, excluding     Ch...
Unicast vs. Anycast DNS   www.domain.com.       1800     IN A X.Y.162.26   domain.com. 1800      IN NS ns1-auth.sprintlink...
~60ms of DNS latency decrease!   ~100ms of page load decrease!
Unicast Domain Pointing to CDNwww.sport.com.        300 IN CNAME www.sport.com.edgesuite.net.sport.com.       172800 IN NS...
~62ms of DNS latency decrease!~75ms of page load decrease, andmore stability!
Unicast + Extra Lookups on GSLB Servers   bank.com.            172800       IN   NS   ns1.bank.com.   bank.com.           ...
~140ms of DNS latency decreaseplus 2 round trips! ~3s of page load decrease!
So, go do some DNS magic to speed up your         site or use DynECT Managed DNS toOptimizing Web Performance By Using Fas...
Questions?    Send me email: tom@dyn.com    Twitter: @tomdyninc | #velocityconfThanks for attending!                      ...
Upcoming SlideShare
Loading in...5
×

Optimizing Web Performance by Using Fast DNS

714
-1

Published on

Your job – make sure your business’s website or ecommerce storefront is running fast and is always available to your customers. Why is this important? Research shows (and we are all aware) of how impatient people are when surfing the Web. Even a .5 millisecond slower response or load time, can mean the difference between a customer and a lost opportunity for conversion. This session will take an in depth look at how companies can architect their network for optimized speed, performance and how top companies have been winning the battle against website latency.

For some DNS is just DNS and they believe there is nothing they can do to improve its performance. But a growing number of informed others are realizing that when you take the time to do a little more research, there is actually a unique and fast way to optimize their website in a variety of ways. This session is for those who understand the importance of their network architecture and are interested in learning how simple changes can optimize performance, speed and ultimately Web driven revenue. All of which lead to an enhanced bottom line.

The session will include:

* An overview of the difference between Unicast and Anycast DNS networks, what the pros and cons of each are, and how you can choose and implement one that works best for your needs.
* A deep dive into how to build and configure a rock solid Anycast network: physics, electronics, routing and monitoring.
* A summary of how all this translates to real world applications with examples from a recent study featuring three popular banking websites and how with changes to their network architecture they would significantly lower their DNS response times.

Published in: Technology, Design
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
714
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
42
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Optimizing Web Performance by Using Fast DNS

  1. 1. Optimizing Web Performance by Using Fast DNSTom DalyChief Scientist, Dyn Labstom@dyn.com | @tomdyninc#velocityconf Dyn.com | @dyninc
  2. 2. Goal of the Talk • Understand the impact of DNS response latency on total web page load time • Understand the trade-offs between Unicast and Anycast DNS architectures • Understand how to deploy Anycast services • Demonstrate benefits through a series of case studiesOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  3. 3. Connecting DNS and HTTP Load Time • Speed metrics: – Google: 400ms => 0.6% search decrease – Shopzilla: 5 seconds => 12% revenue increase – Dyn: Post Velocity 2011 efforts: 55.8% speed improvement • DNS queries are the first blocking operation encountered by your browser’s HTML parser.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  4. 4. Understand the Tradeoffs • HTTP optimizations everywhere! Yslow, ShowSlow, etc. • Many HTTP optimizations ignore DNS impact: – Short TTLs require more queries – Pipelining across host FQDNs require more queries – Multiple CNAMEs in a chain require more queries – GSLB devices require multiple delegations • Legacy DNS architectures + More Queries = More DNS latency overall!Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  5. 5. A Worst Case Scenario! Poor anycast + CDN CNAME chain + back to origin nodeOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  6. 6. Don’t worry, there is hope!Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  7. 7. Easy Wins for WebOps • Higher TTLs mean less queries to keep cache hot, less agility in moving resources around – Not so compatible with today’s movement to cloud. • Less FQDNs mean less queries – Also meaning less opportunity to use pipelining – Careful choice on how much to break out to different FQDNs • Watch for long CNAME chains being usedOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  8. 8. Harder Wins for WebOps • Offline nameservers / Lame delegations – This means timed out queries upstream: 2 or 10 seconds depending upon implementation – For unicast, monitor your DNS extensively • DNS Deployment Approach: – Registrar / Hosting Provider (cost center, no focus) – In-house (Unicast, due to cost) – Managed External DNS (Anycast, focused business driver)Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  9. 9. Hardest Win for WebOps • Self Deploy a Proper DNS Architecture: – For speed and performance, you must deploy anycast DNS. – You need multiple sites for HTTP anyways, but you need LOTs of sites to achieve redundancy with anycast – otherwise useless approach – Then there are LOTs of specific limitations that you don’t deal with in HTTP serving to figure out • Choices: Unicast vs. Anycast DNS…Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  10. 10. Traditional DNS: Unicast • Need to deploy many nameservers for redundancy and geographic diversity. • With Unicast, you get a one to one mapping between domain’s NS records and each nameserver listed. • Non-timed, non-cached queries MUST contact all of the nameservers in the delegation, taking time.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  11. 11. Today’s DNS: Anycast • Again, need to deploy many nameservers for redundancy and geographic diversity. • But with Anycast, we decouple the mapping of NS records to a nameserver. • We reduce the number of NSes in the delegation – reducing timeouts! • We make all of the nameservers much faster, lowering the non-primed, non-cached tax.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  12. 12. The Ultimate Performance Enemy: DNS Protocol Resiliency • When was the last time you saw a DNS query drop, given enough time to resolve? • DNS was designed with crazy protocol level redundancy techniques due to lossy networks of the 1980s – lots of retry mechanisms. • DNS RTT banding requires all nameservers in a delegation to be contacted. An offline NS cause 2-10 seconds of latency in non-cached lookups.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  13. 13. Unicast Experience ns1: Seattle ns4: New York ns2: Palo Alto ns5: Ashburnns3: Los Angeles ns6: MiamiOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  14. 14. Anycast Experience ns1: Seattle ns1: New York ns2: Palo Alto ns2: Ashburnns3: Los Angeles ns3: MiamiOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  15. 15. Handling Site Outages • What happens during an Unicast site outage? – RTT banding timeouts delay DNS query response times, delaying web load times. • What about in Anycast? – BGP routing “pulls” traffic to the next best site.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  16. 16. Unicast Redundancy ns1: Seattle ns4: New York ns2: Palo Alto ns5: Ashburnns3: Los Angeles ns6: MiamiOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  17. 17. Anycast Redundancy ns1: Seattle ns1: New York ns2: Palo Alto ns2: Ashburnns3: Los Angeles ns3: MiamiOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  18. 18. Handling DDoS • What happens during an Unicast DDoS? – Likely, all of the nameservers in the delegation will be enjoying the packet love! • What about in Anycast? – BGP routing “isolates” traffic to the origins of the DDoS. – Attackers are “blinded” from seeing the whole topology.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  19. 19. Unicast DDoS ns1: Seattle ns4: New York ns2: Palo Alto ns5: Ashburnns3: Los Angeles ns6: MiamiOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  20. 20. Anycast DDoS ns1: Seattle ns1: New York ns2: Palo Alto ns2: Ashburnns3: Los Angeles ns3: MiamiOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  21. 21. Anycast sounds pretty awesome, right?Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  22. 22. Deploying Anycast Services • Deploying anycast isn’t easy: – Understanding / capability of BGP routing – Need your own routable PI IP address space – Consistency of connectivity is important to ensure performance – leads to limited colocation options – Data synchronization across the deployment is critical – In-house monitoring is nearly impossibleOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  23. 23. Routing 101 • Backbones and routing protocols: – IGP (OSPF) for internal connections (link state / metric based) – BGP for external connections (distance vector) • Mixing IGP (OSPF) with BGP – OSPF “floods” routes about the network’s interfaces and point to point links throughout the entire network. – iBGP is “stacked” on top using adjacencies formed in OSPF. – eBGP routes get carried through iBGP, with a partial decision factor coming from the OSPF metrics.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  24. 24. Internet Scale Routing AS 2 AS 3 AS 1 AS 4 ns1: New YorkA network is defined as an ASN.BGP is exchanges “best” routesbetween networks.OSPF floods “all” routes inside anetwork. Optimizing Web Performance By Using Fast DNS Dyn.com | @dyninc Tom Daly @tomdyninc #velocityconf
  25. 25. BGP 101 • With BGP, routing information is exchanged between “peers” – routers connected to each other • Only the “best” routes get exchanged, limiting scope of information shared • BGP provides next-hop information along AS-paths only, then the IGP takes over.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  26. 26. BGP Routing AS 2 AS 3 AS 1 AS 4 ns1: New YorkWith BGP, the shortest AS pathis selected as the best path. Optimizing Web Performance By Using Fast DNS Dyn.com | @dyninc Tom Daly @tomdyninc #velocityconf
  27. 27. BGP Routing Example tom@core-01-ewr.dyndns.com> show route www.level3.com inet.0: 409151 destinations, 1656770 routes (409148 active, 0 holddown, 14 hidden) Restart Complete + = Active Route, - = Last Active, * = Both 4.0.0.0/9 *[BGP/170] 10w4d 11:35:04, MED 100, localpref 100 AS path: 3356 I > to 4.53.90.149 via ge-0/0/4.0 [BGP/170] 1w2d 14:18:00, MED 100, localpref 100Prefix AS path: 174 3356 I Best BGP Path > to 38.104.190.53 via ge-0/0/2.0 The BGP path with the lowest number of AS hops traversed is the best path.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  28. 28. OSPF + iBGP 101 • IGP (OSPF) enumerates all potential “paths” and “costs” in the network. • Links between routers are given metrics for traffic engineering – Longer links tend to have higher metrics • OSPF will calculate end-to-end cost for a path through the network • iBGP carries all Internet routes on top, OSPF costs decides the paths to take.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  29. 29. OSPF Routing in AS4 AS 2 AS 3 AS 1 AS 4 ns1: New YorkWithin the ASN, OSPF picks pathsbased upon metric preferences Optimizing Web Performance By Using Fast DNS Dyn.com | @dyninc Tom Daly @tomdyninc #velocityconf
  30. 30. IGP (iBGP + OSPF) Routing inet.0: 414878 destinations, 4526985 routes (413866 active, 19 holddown, 422693 hidden) 208.78.70.0/24 (16 entries, 1 announced) *BGP Preference: 170/-121 Next hop type: Indirect Next hop type: Router, Next hop index: 2100575 Next hop: 129.250.4.69 via ae1.0 State: <Active Int Ext> Local AS: 65000 Peer AS: 65000 Age: 1w2d 10:33:19 Metric: 0 Metric2: 17 Task: BGP_65000.129.250.0.18+???Prefix AS path: 33517 I Communities: 2914:370 2914:1009 2914:2000 2914:3000 Accepted Localpref: 120 Router ID: 129.250.0.18 BGP Preference: 170/-121 IGP Metric2 Next hop type: Indirect Next hop type: Router, Next hop index: 2101345 Next hop: 129.250.2.183 via ae5.0 weight 0x1 State: <NotBest Int Ext> Inactive reason: Not Best in its group - IGP metric Local AS: 65000 Peer AS: 65000 Age: 5d 8:44:14 Metric2: 20 Task: BGP_65000.129.250.0.178+??? AS path: 33517 I Communities: 2914:370 2914:1001 2914:2000 2914:3000 4459:412 Accepted Localpref: 120 Router ID: 129.250.0.178 Optimizing Web Performance By Using Fast DNS Dyn.com | @dyninc Tom Daly @tomdyninc #velocityconf
  31. 31. Anycast, BGP and OSPF • To make Anycast work, you need to: – Understand the impact of BGP peering upon route path selection as traffic is exchanged between ISPs. – Understand the impact of OSPF route selection to ensure traffic is off-ramped at the right spot to your services • BGP-wise: Your transit and peers external routing policies govern your traffic – BGP communities can help “steer” traffic – Peering policy is king! • IGP-wise: Your backbone providers internal routing metrics – Maintenance events can drag traffic around oddly!Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  32. 32. Putting it All Together AS 2 AS 3 AS 1 AS 4 ns1: New York ns1: Los AngelesOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  33. 33. Aut. Systems and IP Addresses • To multihome your network, you need to run BGP; you need an autonomous system number (ASN) • To stay independent of any provider, you need to apply for and obtain your own address space. – You /want/ to have lots of choice – ISPs do funny things!Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  34. 34. Datacenters, IP Transit, and Peering • Consistent ISP connectivity is key to ensure networks take advantage of IGP metrics over regular BGP routing. • Means connecting in carrier neutral facilities (so you have multiple connections) which means more cost, means multiple contracts, access lists, procedures, etc. • Finding consistency IP transit between US/EU and APAC is a difficult challenge (solved by communities) • To achieve performance, you MUST depend upon IGP routing metrics –granular information needed to off- ramp traffic to you in the right spot • Peering networks don’t always appreciate anycast traffic engineering – inconsistent route setsOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  35. 35. Data Synchronization and Monitoring • Two networks are deployed: – First for Anycast services facing TOWARDs users – Second for Unicast data replication in and amongst the application • CAP Theorem kicks in: – Keeping things in sync while making changes becomes very very hard at scale – You enjoy the inter-datacenter latency during replication • Visibility of an anycast network is reduced: – Monitoring from an anycast site means you ONLY see that same site. – Monitoring externally could mean non-deterministic coverage of anycast instances. • This topic is another talk altogether!Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  36. 36. Example Datacenter Configuration ISP #1 ISP #2BGP Announcement:208.78.69.0/24208.78.70.0/24 Routerem0: 208.78.69.140lo0: 208.78.70.1Local LAN: 208.78.69.0/24Static Route: 208.78.70.1 -> 208.78.69.140
  37. 37. Example BGP Peer Config show configuration protocols bgp ... group NTT { type external; peer-as 2914; neighbor 129.250.192.57 { import [ Full-Routes-In ]; export [ Dyn-Anycast Site-Unicast ]; } } group Tata { type external; peer-as 6453; neighbor 209.58.26.53 { import [ Full-Routes-In ]; export [ Dyn-Anycast Site-Unicast ]; } } ...Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  38. 38. Example Routing Policy Config show configuration policy options ... policy-statement Dyn-Anycast { term advertise { from { protocol aggregate; route-filter 208.78.70.0/24 exact; } then accept; } term next-policy { then next policy; } } ... policy-statement Site-Unicast { term advertise { from { protocol aggregate; route-filter 208.78.69.0/24 exact; } then accept; } term next-policy { then next policy; } } ...Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  39. 39. Example Static Route Config show configuration routing-options ... static { route 0.0.0.0/0 next-hop 129.250.192.57; route 208.78.70.1 next-hop 208.78.69.140; ... } aggregate { route 208.78.70.0/24 { as-path { origin igp; } brief; } ... }Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  40. 40. Example Server Config [tom@dns ~]$ ifconfig igb0 igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU, VLAN_HWCSUM,TSO4> ether 00:1b:21:aa:61:d0 inet 208.78.69.140 netmask 0xffffff00 broadcast 208.78.69.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active [tom@dns ~]$ ifconfig lo0 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=3<RXCSUM,TXCSUM> inet 127.0.0.1 netmask 0xffffffff inet 208.78.70.1 netmask 0xffffffffOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  41. 41. Do this Twice and…Anycast And it works for HTTP services too! ISP #1 ISP #2BGP Announcement: BGP Announcement:208.78.69.0/24 208.78.68.0/24208.78.70.0/24 208.78.70.0/24 Router Routerem0: 208.78.69.140 em0: 208.78.68.140lo0: 208.78.70.1 lo0: 208.78.70.1Local LAN: 208.78.69.0/24 Local LAN: 208.78.68.0/24Static Route: 208.78.70.1 -> 208.78.69.140 Static Route: 208.78.70.1 -> 208.78.68.140
  42. 42. Example Improvements • Warning: YMMV! But let’s chat about it. • Monitoring from 50 Catchpoint Nodes, excluding China (too much noise) • Configured www.foo.com as www.foo.com.dynect- demo.com, matching as many DNS parameters as possible. • Some results expected, others were drastic and surprising! • The domains have been obfuscated to protect the innocent.Optimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  43. 43. Unicast vs. Anycast DNS www.domain.com. 1800 IN A X.Y.162.26 domain.com. 1800 IN NS ns1-auth.sprintlink.net. domain.com. 1800 IN NS ns2-auth.sprintlink.net. domain.com. 1800 IN NS ns3-auth.sprintlink.net. domain.com. 1800 IN NS ns-XXX-01.lXXig.com. domain.com. 1800 IN NS ns-XXX-02.lXXig.com. ;; Received 199 bytes from 144.228.255.10#53(ns3-auth.sprintlink.net) in 99 ms www.domain.com.dynect-demo.com. 1800 IN A X.Y.162.26 dynect-demo.com. 86400 IN NS ns4.p13.dynect.net. dynect-demo.com. 86400 IN NS ns2.p13.dynect.net. dynect-demo.com. 86400 IN NS ns1.p13.dynect.net. dynect-demo.com. 86400 IN NS ns3.p13.dynect.net. ;; Received 157 bytes from 204.13.251.13#53(ns4.p13.dynect.net) in 11 msOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  44. 44. ~60ms of DNS latency decrease! ~100ms of page load decrease!
  45. 45. Unicast Domain Pointing to CDNwww.sport.com. 300 IN CNAME www.sport.com.edgesuite.net.sport.com. 172800 IN NS ns40.sport.com.sport.com. 172800 IN NS ns50.sport.com.sport.com. 172800 IN NS ns60.sport.com.;; Received 276 bytes from 209.133.83.36#53(ns60.sport.com) in 45 mswww.sport.com.dynect-demo.com. 300 IN CNAME www.sport.com.edgesuite.net.dynect-demo.com. 172800 IN NS ns1.p13.dynect.net.dynect-demo.com. 172800 IN NS ns3.p13.dynect.net.dynect-demo.com. 172800 IN NS ns2.p13.dynect.net.dynect-demo.com. 172800 IN NS ns4.p13.dynect.net.;; Received 292 bytes from 204.13.250.13#53(ns2.p13.dynect.net) in 18 msOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  46. 46. ~62ms of DNS latency decrease!~75ms of page load decrease, andmore stability!
  47. 47. Unicast + Extra Lookups on GSLB Servers bank.com. 172800 IN NS ns1.bank.com. bank.com. 172800 IN NS ns2.bank.com. bank.com. 172800 IN NS ns05.bank.com. bank.com. 172800 IN NS ns06.bank.com. ;; Received 183 bytes from 192.5.6.30#53(a.gtld-servers.net) in 188 ms www.bank.com. 600 IN CNAME wwwbc.gslb.bank.com. gslb.bank.com. 3600 IN NS dbes1gbx01.bank.com. gslb.bank.com. 3600 IN NS dcss1gbx01.bank.com. gslb.bank.com. 3600 IN NS dbes1gbx02.bank.com. gslb.bank.com. 3600 IN NS dbws1gbx01.bank.com. gslb.bank.com. 3600 IN NS drds1gbx01.bank.com. gslb.bank.com. 3600 IN NS dbws1gbx02.bank.com. gslb.bank.com. 3600 IN NS drds1gbx02.bank.com. ;; Received 370 bytes from 159.53.110.152#53(ns05.bank.com) in 90 msOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  48. 48. ~140ms of DNS latency decreaseplus 2 round trips! ~3s of page load decrease!
  49. 49. So, go do some DNS magic to speed up your site or use DynECT Managed DNS toOptimizing Web Performance By Using Fast DNS Dyn.com | @dynincTom Daly @tomdyninc #velocityconf
  50. 50. Questions? Send me email: tom@dyn.com Twitter: @tomdyninc | #velocityconfThanks for attending! Dyn.com | @dyninc
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×