Cloudflare lower network latency = faster website loads
•
2 likes•427 views
Lower network latency = faster website loads This document discusses how lower network latency leads to faster website loads. It explains that round-trip time (RTT) measures the time for a network request to travel from one point to another and back. Faster protocols like TLS 1.3 can reduce RTT by eliminating handshake rounds. Content delivery networks (CDNs) also reduce latency by caching content closer to users worldwide. New routing technologies like Cloudflare's Argo can improve performance by up to 59% by choosing network paths based on real-time conditions instead of following indirect routes. Overall, the document emphasizes that lower latency is key to optimizing the user experience on the web.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Cloudflare lower network latency = faster website loads
Similar to Cloudflare lower network latency = faster website loads (20)
Recently uploaded
Recently uploaded (20)
Cloudflare lower network latency = faster website loads
- 1. Lower network latency = faster website loads By Vu Long Tran, Customer Success
- 2. // Welcome
- 3. Does anyone know what this is?
- 5. What is the speed of light?
- 6. The speed of light = 299 792 458 m / s 299,792,458 metres per second (approximately 300,000 km/s) - Wikipedia
- 7. Speed of light has not changed
- 8. Bandwidth vs. Latency Source: https://www.igvita.com/2012/07/19/latency-the-new-web-performance-bottleneck/
- 9. Round-trip time (RTT) Round-trip time (RTT) is the duration in milliseconds (ms) it takes for a network request to go from a starting point to a destination and back again to the starting point. More details: https://www.cloudflare.com/learning/cdn/glossary/round-trip-time-rtt/
- 10. How far is 10ms?
- 11. How far is 20ms?
- 12. How far is 50ms?
- 13. You want to be closer to your eyeballs
- 14. You can use a distributed network to be closer to your eyeballs
- 15. Best to have more servers, than just one
- 16. Client requests a file from an origin server
- 17. Client pulls a cached file from the distributed CDN network rather than the origin server
- 18. RTT (round-trip time back & forth) latency numbers: ● From New York, USA - 25ms ● From San Jose, USA - 36ms ● From Frankfurt, Germany - 110ms ● From Tokyo, Japan - 135ms ● From Sydney, Australia - 170ms ● From Singapore - 190ms ● From Mumbai, India - 225ms dejavuguides.com - hosted on Blogger.com
- 19. dejavuguides.com - using a CDN [VuLong@Vus-MacBook-Air ~]$ ping dejavuguides.com -c 50 PING dejavuguides.com (104.16.113.229): 56 data bytes 64 bytes from 104.16.113.229: icmp_seq=0 ttl=55 time=3.704 ms ... 64 bytes from 104.16.113.229: icmp_seq=42 ttl=55 time=3.755 ms --- dejavuguides.com ping statistics --- 50 packets transmitted, 50 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 3.676/4.105/5.107/0.358 ms
- 20. Example ping to 1.1.1.1 [VuLong@Vus-MacBook-Air ~]$ ping 1.1.1.1 -c 50 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=55 time=4.938 ms ... 64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=5.028 ms --- 1.1.1.1 ping statistics --- 50 packets transmitted, 50 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 4.643/5.398/7.026/0.494 ms
- 21. So how fast do you think can you process incoming data?
- 24. The fastest rate at which humans appear to be able to process incoming visual stimuli is about 13 ms
- 25. So when you're gaming
- 26. So when you're gaming ● 300ms < game is unplayable ● 150ms < game play degraded ● 100ms < player performance affected ● 50ms > target performance ● 13ms > lower detectable limit
- 27. For a browser to download a web page over HTTPS, it needs to: Phase 1: DNS Lookup Phase 2: TCP Handshake (1 round trip) Phase 3: TLS Handshake (up to 2 round trips*) Phase 4: HTTP (1 round trip)
- 28. So this inherently introduces latency
- 30. Round-trip time (RTT) New Connections: TLS 1.2 (and earlier) 4 RTT + DNS TLS 1.3 3 RTT + DNS TLS 1.3 + 0-RTT 3 RTT + DNS Resumed Connections: TLS 1.2 (and earlier) 3 RTT + DNS TLS 1.3 3 RTT + DNS TLS 1.3 + 0-RTT 2 RTT + DNS
- 32. TLS 1.3 has one less handshake More information here - https://blog.cloudflare.com/why-iot-is-insecure
- 33. TLS 1.3 + 0 RTT is even faster See video - https://vimeo.com/208331620
- 34. 330ms vs 502ms
- 36. // The internet
- 37. Internet is interconnected networks
- 38. You can view submarine cable map across the world Submarine Cable Map www.submarinecablemap.com
- 39. You can view data centers across the world www.datacentermap.com
- 40. Internet = BGP Internet uses BGP (Border Gateway Protocol) protocol for making routing decisions across the internet
- 41. It's based on the System of Trust
- 42. Systems of Trust relies on ISPs ISPs have many goals in mind, when making routing decisions including: • High availability • Lower latency/ Packet loss • Minimising traffic cost • Maximising revenue
- 43. So what often happens?
- 44. Routing decisions may take detours
- 45. Routing decisions may avoid tollways
- 46. These routing decisions result in website performance challenges Origin Congested Network Path Unreliable Connection Slow Loading Times Static routes can't avoid congested network paths or unreliable connections Poor User Experience Slow loading times and connection timeouts increase the likelihood of a poor user experience that can result in reduced revenue or damaged brand reputation © 2018 Cloudflare Inc. All rights reserved.
- 47. Is there anything you can do about it?
- 48. Origin Connection Reuse Minimize latency imposed by TCP connection-setup Congestion Avoidance Routing decisions using real-world network conditions You can try Argo Smart Routing Congested Network Path Unreliable Connection Faster Loading Times Cloudflare routes over 10% of all HTTP Internet traffic providing Argo with real world intelligence on the fastest network paths. Internet node / hop Cloudflare Data Centers Cloudflare’s private network 10Tbps throughput, with 151+ PoPs in 74+ countries © 2018 Cloudflare Inc. All rights reserved.
- 50. Argo Smart Routing Sample Results
- 52. // Examples of better routing decisions at play
- 53. Sketchers.com US - Argo 200ms perf increase Source: https://twitter.com/m242/status/866683565286633472
- 54. absolutemusic.co.uk - ˜1.54 sec to ˜600 ms Source: https://twitter.com/BobSpadger/status/866906385715482624
- 55. Stewardmedia.com.au - 50% perf increase Source: https://twitter.com/jimboot/status/872750354986815489
- 56. Australian customer - 54% faster This customer in Australia saw an increase performance improve from 455ms to 208ms.
- 57. Indian customer - 31% faster This customer in India saw performance improve from 623ms to 341ms.
- 58. Indian customer - 45% faster This customer in India saw performance improve from 623ms to 341ms.
- 59. Thailand customer - 59% faster This customer in Thailand saw performance improve from 761ms to 313ms.
- 60. Takeaways • The internet does not naturally always use the shortest routing path • Consider using a content delivery network rather than one origin server alone
- 62. // Useful links More information
- 63. Useful links • TLS 1.3 over TLS 1.2 (leaner protocol, fewer packets needed to get started) https://blog.cloudflare.com/introducing-tls-1-3 • TLS 1.3 bonus - 0-RTT for repeat visitors https://blog.cloudflare.com/introducing-0- rtt • Introducing Argo overview — A faster, more reliable, more secure Internet for everyone - https://blog.cloudflare.com/argo
- 64. // Thank you! Vu Long Tran Customer Success, Singapore office vulong@cloudflare.com Twitter: @vulongtran