From: Michael Richardson <mcr@sandelman.ca>
To: Sina Khanifar <sina@waveform.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Updated Bufferbloat Test
Date: Fri, 26 Feb 2021 12:25:56 -0500 [thread overview]
Message-ID: <31136.1614360356@localhost> (raw)
In-Reply-To: <CABF4YOXtYsTkMLvPEdfDK4LA2+9beXA9sK_3WE99zmWaReDZhw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
Sina Khanifar <sina@waveform.com> wrote:
> I think that given this limitation of browser-based tests, maybe the
> users you have in mind are not our target audience. Our goal is to make
> an easy-to-use bufferbloat test "for the rest of us." For
> technically-minded gamers, running flent will likely give much better
> results. I'd love for it to be otherwise, so we may try to tinker with
> things to see if we can get CPU usage down and simultaneously deal with
> the UDP question below.
I think that your goals are good.
In many cases around here, the higher speed connections are also more bloated,
and the challenge is convincing a home owner that they will get better
interactive performance on a VDSL2 than a FTTH, if they upgrade their router.
(This is particularly true if their wifi is slower than their downlink, and
also bloated)
It's about quality over quantity.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2021-02-26 17:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 18:22 Sina Khanifar
2021-02-24 22:10 ` Dave Taht
2021-02-24 23:39 ` Simon Barber
2021-02-25 5:56 ` Sina Khanifar
2021-02-25 7:15 ` Simon Barber
2021-02-25 7:32 ` Sina Khanifar
2021-02-25 13:38 ` Simon Barber
2021-02-25 13:43 ` Dave Taht
2021-02-25 13:49 ` Mikael Abrahamsson
2021-02-25 13:53 ` Simon Barber
2021-02-25 19:47 ` Sina Khanifar
2021-02-25 19:56 ` Simon Barber
2021-02-25 20:10 ` Sina Khanifar
2021-02-25 20:52 ` Simon Barber
2021-02-25 20:53 ` Simon Barber
2021-02-25 13:46 ` Simon Barber
2021-02-25 7:20 ` Simon Barber
2021-02-25 10:51 ` Sebastian Moeller
2021-02-25 20:01 ` Sina Khanifar
2021-02-25 20:14 ` Sebastian Moeller
2021-02-26 1:06 ` Daniel Lakeland
2021-02-26 8:20 ` Sina Khanifar
2021-02-26 17:25 ` Michael Richardson [this message]
2021-02-24 22:15 ` Kenneth Porter
2021-02-25 5:29 ` Kenneth Porter
2021-02-25 5:35 ` Dave Taht
2021-02-25 6:24 ` Kenneth Porter
2021-02-25 1:16 ` David Collier-Brown
2021-02-25 6:21 ` Sina Khanifar
2021-02-25 4:48 ` Marco Belmonte
[not found] ` <1D68EF40C3A8A269831408C8@172.27.17.193>
2021-02-25 5:58 ` Sina Khanifar
2021-02-25 9:47 ` Mikael Abrahamsson
2021-02-25 10:49 ` Sebastian Moeller
2021-02-25 20:41 ` Sina Khanifar
2021-02-25 20:50 ` Sina Khanifar
2021-02-25 21:15 ` Sebastian Moeller
2021-02-26 8:23 ` Sina Khanifar
2021-02-26 18:41 ` Sina Khanifar
2021-02-26 19:58 ` Sebastian Moeller
2021-02-25 12:27 ` Toke Høiland-Jørgensen
2021-02-25 14:48 ` Toke Høiland-Jørgensen
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=31136.1614360356@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=sina@waveform.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