From: Sam Westwood <sam@repeaterstore.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] We built a new bufferbloat test and keen for feedback
Date: Wed, 4 Nov 2020 21:30:14 +0000 [thread overview]
Message-ID: <CABks0J1r+bG7LoPhkn+rwz+72pDWdzGtdVCR+6=v+AobuXgrjA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2643 bytes --]
Hi everyone,
My name is Sam and I'm the co-founder and COO of Waveform.com. At Waveform
we provide equipment to help improve cell phone service, and being in the
industry we've always been interested in all aspects of network
connectivity. Bufferbloat for us has always been interesting, and while
there are a few tests out there we never found one that was fantastic. So
we thought we'd try and build one!
My colleague Arshan has built the test, which we based upon the Cloudflare
Speedtest template that was discussed earlier in the summer in a previous
thread.
We measure bufferbloat under two conditions: when downlink is saturated and
when uplink is saturated. The test involves three stages: Unloaded,
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 measuring latency. In
the third stage we do the same but for upload. Both download and upload
usually take around 5 seconds. We show the median, first quartile and the
third quartile on distribution charts corresponding to each stage to
provide a visual representation of the latency variations. For download and
upload we have used Cloudflare's speedtest backend.
You can find the test here: https://www.waveform.com/apps/dev-arshan
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.
This is a really early alpha, and so we are keen to get any and all
feedback you have :-). Things that we would particularly like feedback on:
- How does the bufferbloat measure compare to other tests you may have
run on the same connection (e.g. dslreports, fast.com)
- How the throughput results (download/upload/latency) look compared to
other tools
- Any feedback on the user interface of the test itself? We know that
before releasing more widely we will put more effort into explaining
bufferbloat than we have so far.
- Anything else you would like to give feedback on?
We have added a feature to share results via a URL, so please feel free to
share these if you have specific feedback.
Thanks!
Sam and Arshan
*************************
Sam Westwood
Co-Founder & COO | RSRF & Waveform
E sam@waveform.com
D (949) 207-3175
T 1-800-761-3041 Ext. 100
W www.rsrf.com & www.waveform.com
[-- Attachment #2: Type: text/html, Size: 3251 bytes --]
next reply other threads:[~2020-11-04 21:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 21:30 Sam Westwood [this message]
2020-11-04 23:43 ` Michael Richardson
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='CABks0J1r+bG7LoPhkn+rwz+72pDWdzGtdVCR+6=v+AobuXgrjA@mail.gmail.com' \
--to=sam@repeaterstore.com \
--cc=bloat@lists.bufferbloat.net \
/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