Download to read offline
![Results
Normal HTTP Request
Server Software: Apache
Server Hostname: www.meetme.com
Server Port: 80
Document Path: /
Document Length: 30332 bytes
Time taken for tests: 4.202 seconds
Total transferred: 316049 bytes
HTML transferred: 303307 bytes
Requests per second: 2.38 [#/sec] (mean)
Time per request: 420.232 [ms] (mean)
Transfer rate: 73.45 [Kbytes/sec]
Proxyed HTTP Request
Server Software: Apache
Server Hostname: www.meetme.com
Server Port: 3300
Document Path: /
Document Length: 30259 bytes
Time taken for tests: 2.197 seconds
Total transferred: 315326 bytes
HTML transferred: 302582 bytes
Requests per second: 4.55 [#/sec] (mean)
Time per request: 219.739 [ms] (mean)
Transfer rate: 140.14 [Kbytes/sec]](https://image.slidesharecdn.com/packetsfromtheair-140818160918-phpapp02/75/Packets-Falling-From-The-Air-74-2048.jpg)
Uploaded byJeremy Stinson
Packets Falling From The Air
The document discusses latency in network operations, measuring the time taken for data packets to travel between a source and a receiver, emphasizing that lower latency results in better performance. Various scenarios and impacts on latency are detailed, including comparisons between different mobile networks and protocols like TCP and HTTP. Recommendations for improving latency involve limiting API endpoints, DNS queries, and employing optimizations like HTTP keepalive and websocket usage.
![Number_Guessing_Game_Dsbsbssbzboc[1].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/numberguessinggamedoc1-251206215042-a076fc05-thumbnail.jpg?width=640&height=640&fit=bounds)
Packets Falling From The Air
- 1. Packets Falling fromthe Air Jeremy Stinson VP of Network Operations MeetMe @jstinson
- 2. Cheesy jokes will follow,continue at your own risk!!!
- 7. Latency is definedas the time it takes for a source to send a packet of data to a receiver. Latency is typically measure in milliseconds. The lower the latency (the fewer the milliseconds), the better the network performance.
- 9. Data from OpenSignal(Feb 2014) 0 20 40 60 80 100 120 LTE LTE LTE LTE AT&T Sprint T-Mobile Verizon LTE Mean Latency (ms)
- 10. Data from OpenSignal(Feb 2014) 0 50 100 150 200 250 AT&T T-Mobile AT&T T-Mobile AT&T T-Mobile Sprint Verizon Sprint Verizon UMTS HSPAP HSPA EVDO A eHRPD 3G Mean Latency (ms)
- 11.
- 30. When is the speedof light not the speed of light?
- 32.
- 33. I tried tocome up with an IPv4 joke, but the good ones were all already exhausted…
- 36. Didn’t we runout of IPv4 jokes?
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45. So what whatdoes this mean?
- 46.
- 47.
- 48.
- 49.
- 50.
- 51. 45ms + 200ms HTTP 200… 90m s
- 52. So how muchworse is this going to be?
- 53. 45 + 90 45+ 90 45 + 90 45 + 90 + 200 ------------- 740ms
- 54. 740 - 380= 360ms
- 55. What about 3Gor worse?
- 56. 45 + 150 45+ 150 45 + 150 45 + 150 + 200 ------------- 980ms 3G sucks more
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 64. What lessons can welearn from this?
- 65. Limit the number ofAPI endpoints
- 66.
- 67.
- 68.
- 69.
- 70.
- 72.
- 73.
- 74. Results Normal HTTP Request ServerSoftware: Apache Server Hostname: www.meetme.com Server Port: 80 Document Path: / Document Length: 30332 bytes Time taken for tests: 4.202 seconds Total transferred: 316049 bytes HTML transferred: 303307 bytes Requests per second: 2.38 [#/sec] (mean) Time per request: 420.232 [ms] (mean) Transfer rate: 73.45 [Kbytes/sec] Proxyed HTTP Request Server Software: Apache Server Hostname: www.meetme.com Server Port: 3300 Document Path: / Document Length: 30259 bytes Time taken for tests: 2.197 seconds Total transferred: 315326 bytes HTML transferred: 302582 bytes Requests per second: 4.55 [#/sec] (mean) Time per request: 219.739 [ms] (mean) Transfer rate: 140.14 [Kbytes/sec]
- 75.
- 76.
- 77.
- 79.
- 80.
- 81.
- 82.
- 86.
- 88. The problem withSSL jokes is that you must get someone else to vouch for you before you can tell the joke.
- 92. SPDY • Connection multiplexing •Multiple Requests per connection • Out of order responses • Compress HTTP Headers • Server side push
- 96.
- 98.
Editor's Notes
- #6 ----- Meeting Notes (7/29/14 18:36) ----- There is limit gain after a certain point
- #13 Lay their towers in a grid formation so that their licensed frequencies do not overlap ----- Meeting Notes (7/29/14 18:57) ----- 1. Each carrier goes through a auction system to purchase free frequencies, the more frequencies the denser you can get. 2. Frequencies are laid out in a grid to prevent overlap which allows the carrier to re-use the same frequencies in the region
- #14 ----- Meeting Notes (7/29/14 18:57) ----- 1. phone comes out of sleep mode, negotiates a frequency to use with the local tower, and data can start being sent out
- #15 ----- Meeting Notes (7/29/14 18:57) ----- Conveintly near you, different atteneas are used for different technologies (LTE vs 3g, etc)
- #18 ----- Meeting Notes (7/29/14 18:57) ----- translates data from LTE to ethernet and sends it out
- #21 ----- Meeting Notes (7/29/14 18:57) ----- local pop
- #35 3g, 4g, and LTE are all over IP from the beginning, LTE is native IPv6. Why is this important?
- #36 EVIL!!!!
- #58 DNS lookup
- #59 First Request
- #60 Another DNS lookup
- #61 Facebook auth
- #62 Final data set
- #74 First Request
- #80 First Request
- #81 First Request
- #82 First Request
- #93 Header compression resulted in an ~88% reduction in the size of request headers and an ~85% reduction in the size of response headers. On the lower-bandwidth DSL link, in which the upload link is only 375 Kbps, request header compression in particular, led to significant page load time improvements for certain sites (i.e. those that issued large number of resource requests). We found a reduction of 45 - 1142 ms in page load time simply due to header compression
- #98 MPTCP is intended to create more robust connections, resistant to path failures, and to improve performance, especially for delay-sensitive applications such as voice