Sam Westwood <sam@repeaterstore.com> wrote:
    > Downlink Saturated, and Uplink Saturated. In the first stage we simply
    > measure latency to a file hosted on a CDN. This is usually around 5ms
    > and could vary a bit based on the user's location. We use the webTiming
    > API to find the time-to-first-byte, and consider that as the
    > latency. In the second stage we run a download, while simultaneously

Just to clarify:
  the latency measurement involves a TCP three-way handshake, with
  the fourth packet providing the end of the process.
  No TLS, I hope?

    > We built testing it on Chrome, but it works on Firefox and mobile
    > too. On mobile results may be a little different, as the APIs aren't
    > available and so instead we implemented a more manual method, which can
    > be a little noisier.

Would webrtc APIs have helped?


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide