From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Sam Westwood <sam@repeaterstore.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] We built a new bufferbloat test and keen for feedback
Date: Wed, 04 Nov 2020 18:43:25 -0500 [thread overview]
Message-ID: <19611.1604533405@localhost> (raw)
In-Reply-To: <CABks0J1r+bG7LoPhkn+rwz+72pDWdzGtdVCR+6=v+AobuXgrjA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-11-04 23:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 21:30 Sam Westwood
2020-11-04 23:43 ` Michael Richardson [this message]
2020-11-04 23:54 ` Toke Høiland-Jørgensen
2020-11-05 1:52 ` Y
2020-11-05 0:23 ` Dave Collier-Brown
2020-11-05 11:48 ` Toke Høiland-Jørgensen
2020-11-05 13:24 ` [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback) Dave Collier-Brown
2020-11-05 14:24 ` Toke Høiland-Jørgensen
2020-11-05 16:06 ` Arshan Khanifar
2020-11-05 17:25 ` Toke Høiland-Jørgensen
2020-11-06 16:03 ` Stephen Hemminger
2020-11-06 16:17 ` Toke Høiland-Jørgensen
2020-11-06 17:05 ` Sebastian Moeller
2020-11-08 22:07 ` Arshan Khanifar
2020-11-14 3:37 ` Dave Taht
2020-11-14 23:14 ` Michael Richardson
2020-11-05 8:21 ` [Bloat] We built a new bufferbloat test and keen for feedback Sebastian Moeller
2020-11-05 21:30 ` Sam
2020-11-07 21:22 Rich Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19611.1604533405@localhost \
--to=mcr+ietf@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=sam@repeaterstore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox