Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Measuring latency from the browser


Published on

Measuring latency from the browser, by Agustin Formoso.

A presentation given at the APNIC 40 Lightning Talks session on Tue, 8 Sep 2015.

Published in: Internet
  • Login to see the comments

Measuring latency from the browser

  1. 1. Measuring latency from the browser Agustín Formoso LACNIC Labs
  2. 2. @proyectosimon The project The problem • Connectivity in LAC is good but not optimal • Presence of IXPs, but inter- country connectivity still has to be improved • Information about connectivity is not easy to find or updated The solution • Objective
 Provide representative and up-to-date connectivity measurements to anyone interested in them • How
 Latency measurements from many origins, to many destinations, via different protocols
  3. 3. @proyectosimon Why bother with the browser? Pros • Standard and widely-used technologies • Ran at the end user • Can trigger measurements automatically • Scales fast Cons • Browser and operating system combination differences - TCP connections are handled differently by browser and OS combination! - Browser Javascript engines vary - OSes handle processes differently • Need of normalising different environments!
  4. 4. @proyectosimon Why bother with the browser?
  5. 5. @proyectosimon Testing our tool in Browserstack • Cloud-based testing service aimed at web developers to check the look & feel and responsiveness of their sites • We use it to run our Javascript tool over many different OS and browser combination
 • We used automated Selenium tests
  6. 6. @proyectosimon The test: Javascript tool • Ran in the virtual instance • Fixed origin, fixed destination • Simple HTTP GET • Time the RTT • Parallel sessions with a reference environment always present
  7. 7. @proyectosimon Normalising results Windows 7 Windows 8.1 OS X Windows XP Windows 8 Chrome family 0 +1.9 -7.2 -1.4 +0.1 Firefox
 family -3.9 -2.8 -11.4 -4.8 -5.6 Our reference environment[Results are in ms]
  8. 8. @proyectosimon Normalising results • Two distinct behaviours - Firefox vs. Chrome - OS X versus the rest [Lighter blue means faster]
  9. 9. @proyectosimon LAC regional matrix [Lighter blue means faster]
  10. 10. @proyectosimon Still… • We need more tests! (currently at ~1.5K daily) • Uncertainties on virtualisation • No mobile or Linux yet (~8% of seen traffic)
  11. 11. @proyectosimon Conclusions • The browser: great tool for delivering large-scale measurements but - Huge variety - Measurement noise can be high
  12. 12. Thank you! Q&A