Sf perf
0 likes437 views
The document discusses techniques for improving website performance through modifications to DNS. It describes how serial HTTP loading is slower than parallel loading due to round trip times for DNS lookups. It then evaluates options for implementing parallel DNS lookups, including using CNAME records to alias multiple hostnames to a single IP address, and placing additional IP addresses in the answer or additional sections of DNS responses to allow parallel hostname resolutions. While these techniques could improve performance, they may violate DNS standards or caching assumptions.
Sf perf
- 1. Doing Horrible Things to DNS (in the name of science) @sh1mmer SF Perf Meetup Thursday, September 23, 2010
- 2. The basics of DNS Thursday, September 23, 2010
- 3. Thursday, September 23, 2010
- 4. Thursday, September 23, 2010
- 5. Thursday, September 23, 2010
- 6. Thursday, September 23, 2010
- 7. Thursday, September 23, 2010
- 8. San Francisco - Mission Branch Thursday, September 23, 2010
- 9. Thursday, September 23, 2010
- 10. Thursday, September 23, 2010
- 11. San Francisco - Main Library Thursday, September 23, 2010
- 12. Thursday, September 23, 2010
- 13. Thursday, September 23, 2010
- 14. New York City - 5th & 42nd Branch Thursday, September 23, 2010
- 15. Thursday, September 23, 2010
- 16. Thursday, September 23, 2010
- 17. New York City - 5th & 42nd Branch Thursday, September 23, 2010
- 18. Thursday, September 23, 2010
- 19. San Francisco - Main Library Thursday, September 23, 2010
- 20. San Francisco - Main Library Thursday, September 23, 2010
- 21. Thursday, September 23, 2010
- 22. San Francisco - Mission Branch Thursday, September 23, 2010
- 23. San Francisco - Mission Branch Thursday, September 23, 2010
- 24. Thursday, September 23, 2010
- 25. Thursday, September 23, 2010
- 26. Thursday, September 23, 2010
- 27. Thursday, September 23, 2010
- 28. DNS for performance Thursday, September 23, 2010
- 29. Page Load Time vs. Bandwidth Thursday, September 23, 2010
- 30. Page Load Time vs. Round Trip Time Thursday, September 23, 2010
- 31. Trend Curves for Bandwidth vs. RTT Thursday, September 23, 2010
- 32. Serial HTTP loading Thursday, September 23, 2010
- 33. Parallel HTTP loading Thursday, September 23, 2010
- 34. Why not just use a bunch of domains? Thursday, September 23, 2010
- 35. DNS Querying Thursday, September 23, 2010
- 36. Ideal? 1 domain many threads Thursday, September 23, 2010
- 37. Option 1: SPDY Thursday, September 23, 2010
- 38. Good: Multi-thread TCP connections Bad: Only works on Chrome Thursday, September 23, 2010
- 39. Option 2: Do horrible things to DNS Thursday, September 23, 2010
- 40. Good: Works now Bad: Might have to violate RFCs Thursday, September 23, 2010
- 41. Option 2a - Mucking about with C names Thursday, September 23, 2010
- 42. CNAMES are hosts which are aliases of other hosts Thursday, September 23, 2010
- 43. ajax1.hackerhouse.org. 1800 IN CNAME ajax2.hackerhouse. ajax2.hackerhouse.org. 1800 IN CNAME ajax3.hackerhouse. ajax3.hackerhouse.org. 1800 IN CNAME ajax4.hackerhouse. ajax4.hackerhouse.org. 1800 IN CNAME ajax5.hackerhouse. ajax5.hackerhouse.org. 1800 IN CNAME ajax.hackerhouse. ajax.hackerhouse.org. 1800 IN A 127.0.0.1 Thursday, September 23, 2010
- 44. We now have 6 hostnames Thursday, September 23, 2010
- 45. Good: 6 hostnames Bad: Inflexible Thursday, September 23, 2010
- 46. Option 2b - Doing weird things with RRs Thursday, September 23, 2010
- 47. RR is the section of a DNS response which contains the HOST records Thursday, September 23, 2010
- 48. ;; QUESTION SECTION: ;ajax.hackerhouse.org. IN A ;; ANSWER SECTION: ajax.hackerhouse.org. 60 IN A 184.106.231.91 Thursday, September 23, 2010
- 49. ;; QUESTION SECTION: ;ajax.hackerhouse.org. IN A ;ajax1.hackerhouse.org. IN A ;ajax2.hackerhouse.org. IN A ;; ANSWER SECTION: ajax.hackerhouse.org. 60 IN A 184.106.231.91 ajax1.hackerhouse.org. 60 IN A 184.106.231.90 ajax2.hackerhouse.org. 60 IN A 184.106.231.89 Thursday, September 23, 2010
- 50. ;; QUESTION SECTION: ;ajax.hackerhouse.org. IN A ;; ANSWER SECTION: ajax.hackerhouse.org. 60 IN A 184.106.231.91 ;; ADDITIONAL SECTION: ajax1.hackerhouse.org. 60 IN A 184.106.231.90 ajax2.hackerhouse.org. 60 IN A 184.106.231.89 Thursday, September 23, 2010
- 51. Good: Flexible Bad: Caching /Violating RFCs Thursday, September 23, 2010