From: Bruce Perens <bruce@perens.com>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>,
rjmcmahon <rjmcmahon@rjmcmahon.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Starlink] [Rpm] the grinch meets cloudflare's christmas present
Date: Wed, 4 Jan 2023 15:54:37 -0800 [thread overview]
Message-ID: <CAK2MWOsGZ1bzHJj+FA=jDLucsZ7OvqBYRAq5eM_arBrBT+ZNYQ@mail.gmail.com> (raw)
In-Reply-To: <SY4PR01MB6979574D1855F32A8B8F0DC6CEF59@SY4PR01MB6979.ausprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 4941 bytes --]
On the other hand, we would like to be comprehensible to normal users,
especially when we want them to press their providers to deal with
bufferbloat. Differences like speed and rate would go right over their
heads.
On Wed, Jan 4, 2023 at 1:16 PM Ulrich Speidel via Starlink <
starlink@lists.bufferbloat.net> wrote:
> The use of the term "speed" in communications used to be restricted to the
> speed of light (or whatever propagation speed one happened to be dealing
> with. Everything else was a "rate". Maybe I'm old-fashioned but I think
> talking about "speed tests" muddies the waters rather a lot.
>
> --
> ****************************************************************
> Dr. Ulrich Speidel
>
> Department of Computer Science
>
> Room 303S.594
> Ph: (+64-9)-373-7599 ext. 85282
>
> The University of Auckland
> u.speidel@auckland.ac.nz
> http://www.cs.auckland.ac.nz/~ulrich/
> ****************************************************************
> ------------------------------
> *From:* Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of
> rjmcmahon via Starlink <starlink@lists.bufferbloat.net>
> *Sent:* Thursday, January 5, 2023 9:02 AM
> *To:* jf@jonathanfoulkes.com <jf@jonathanfoulkes.com>
> *Cc:* Cake List <cake@lists.bufferbloat.net>; IETF IPPM WG <ippm@ietf.org>;
> libreqos <libreqos@lists.bufferbloat.net>; Dave Taht via Starlink <
> starlink@lists.bufferbloat.net>; Rpm <rpm@lists.bufferbloat.net>; bloat <
> bloat@lists.bufferbloat.net>
> *Subject:* Re: [Starlink] [Rpm] the grinch meets cloudflare's christmas
> present
>
> Curious to why people keep calling capacity tests speed tests? A semi at
> 55 mph isn't faster than a porsche at 141 mph because its load volume is
> larger.
>
> Bob
> > HNY Dave and all the rest,
> >
> > Great to see yet another capacity test add latency metrics to the
> > results. This one looks like a good start.
> >
> > Results from my Windstream DOCSIS 3.1 line (3.1 on download only, up
> > is 3.0) Gigabit down / 35Mbps up provisioning. Using an IQrouter Pro
> > (an i5 x86) with Cake set for 710/31 as this ISP can’t deliver
> > reliable low-latency unless you shave a good bit off the targets. My
> > local loop is pretty congested.
> >
> > Here’s the latest Cloudflare test:
> >
> >
> >
> >
> > And an Ookla test run just afterward:
> >
> >
> >
> >
> > They are definitely both in the ballpark and correspond to other tests
> > run from the router itself or my (wired) MacBook Pro.
> >
> > Cheers,
> >
> > Jonathan
> >
> >
> >> On Jan 4, 2023, at 12:26 PM, Dave Taht via Rpm
> >> <rpm@lists.bufferbloat.net> wrote:
> >>
> >> Please try the new, the shiny, the really wonderful test here:
> >> https://speed.cloudflare.com/
> >>
> >> I would really appreciate some independent verification of
> >> measurements using this tool. In my brief experiments it appears - as
> >> all the commercial tools to date - to dramatically understate the
> >> bufferbloat, on my LTE, (and my starlink terminal is out being
> >> hacked^H^H^H^H^H^Hworked on, so I can't measure that)
> >>
> >> My test of their test reports 223ms 5G latency under load , where
> >> flent reports over 2seconds. See comparison attached.
> >>
> >> My guess is that this otherwise lovely new tool, like too many,
> >> doesn't run for long enough. Admittedly, most web objects (their
> >> target market) are small, and so long as they remain small and not
> >> heavily pipelined this test is a very good start... but I'm pretty
> >> sure cloudflare is used for bigger uploads and downloads than that.
> >> There's no way to change the test to run longer either.
> >>
> >> I'd love to get some results from other networks (compared as usual to
> >> flent), especially ones with cake on it. I'd love to know if they
> >> measured more minimum rtts that can be obtained with fq_codel or cake,
> >> correctly.
> >>
> >> Love Always,
> >> The Grinch
> >>
> >> --
> >> This song goes out to all the folk that thought Stadia would work:
> >>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> >> Dave Täht CEO, TekLibre, LLC
> >>
> <image.png><tcp_nup-2023-01-04T090937.211620.LTE.flent.gz>_______________________________________________
> >> Rpm mailing list
> >> Rpm@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/rpm
> >
> >
> > _______________________________________________
> > Rpm mailing list
> > Rpm@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/rpm
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
Bruce Perens K6BP
[-- Attachment #2: Type: text/html, Size: 8553 bytes --]
next prev parent reply other threads:[~2023-01-04 23:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 17:26 [Bloat] " Dave Taht
2023-01-04 19:20 ` [Bloat] [Rpm] " jf
2023-01-04 20:02 ` rjmcmahon
2023-01-04 20:11 ` David Collier-Brown
2023-01-04 23:00 ` Stephen Hemminger
[not found] ` <SY4PR01MB6979574D1855F32A8B8F0DC6CEF59@SY4PR01MB6979.ausprd01.prod.outlook.com>
2023-01-04 22:12 ` [Bloat] [Starlink] " Dick Roy
2023-01-05 6:06 ` rjmcmahon
2023-01-04 23:54 ` Bruce Perens [this message]
2023-01-05 6:11 ` rjmcmahon
2023-01-05 16:19 ` Michael Richardson
2023-01-05 11:11 ` [Bloat] " Sebastian Moeller
2023-01-06 0:30 ` [Bloat] [Starlink] [Rpm] the grinch meets cloudflare'schristmas present Dick Roy
2023-01-06 2:33 ` rjmcmahon
2023-01-06 9:55 ` Sebastian Moeller
2023-01-05 4:25 ` [Bloat] [Starlink] [Rpm] the grinch meets cloudflare's christmas present Dick Roy
2023-01-06 16:38 ` [Bloat] [LibreQoS] " MORTON JR., AL
2023-01-06 20:38 ` [Bloat] [Rpm] " rjmcmahon
2023-01-06 20:47 ` rjmcmahon
2023-01-06 23:29 ` [Bloat] [Starlink] [Rpm] [LibreQoS] the grinch meets cloudflare'schristmas present Dick Roy
2023-01-06 23:44 ` rjmcmahon
2023-01-07 0:31 ` Dick Roy
2023-01-10 17:24 ` Luis A. Cornejo
2023-01-11 5:07 ` [Bloat] [Rpm] [Starlink] " Dave Taht
2023-01-11 11:05 ` Jay Moran
2023-01-12 16:01 ` Luis A. Cornejo
2023-01-12 16:12 ` Dave Taht
2023-01-12 16:20 ` Luis A. Cornejo
2023-01-12 17:42 ` MORTON JR., AL
2023-01-13 3:28 ` Luis A. Cornejo
2023-01-13 3:47 ` Luis A. Cornejo
2023-01-13 4:01 ` Dave Taht
2023-01-13 14:08 ` Luis A. Cornejo
2023-01-13 3:30 ` Luis A. Cornejo
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='CAK2MWOsGZ1bzHJj+FA=jDLucsZ7OvqBYRAq5eM_arBrBT+ZNYQ@mail.gmail.com' \
--to=bruce@perens.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jf@jonathanfoulkes.com \
--cc=rjmcmahon@rjmcmahon.com \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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