General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
	libreqos <libreqos@lists.bufferbloat.net>,
	Cake List <cake@lists.bufferbloat.net>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	Rpm <rpm@lists.bufferbloat.net>, IETF IPPM WG <ippm@ietf.org>
Subject: Re: [Bloat] [Rpm] the grinch meets cloudflare's christmas present
Date: Wed, 4 Jan 2023 14:20:15 -0500	[thread overview]
Message-ID: <845161E4-474C-44A9-92D4-1702748A3DA1@jonathanfoulkes.com> (raw)
In-Reply-To: <CAA93jw4sbPeZ42eTLQzPmg_-viBBtbdQogAMgMNndoEHjY5UNA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

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:


[-- Attachment #2: CFSpeedTest_Gig35_20230104.png --]
[-- Type: image/png, Size: 379539 bytes --]

[-- Attachment #3: Type: text/plain, Size: 41 bytes --]



And an Ookla test run just afterward:


[-- Attachment #4: Speedtest_net_Gig35_20230104.png --]
[-- Type: image/png, Size: 40589 bytes --]

[-- Attachment #5: Type: text/plain, Size: 1897 bytes --]



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


  reply	other threads:[~2023-01-04 19:20 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 ` jf [this message]
2023-01-04 20:02   ` [Bloat] [Rpm] " 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
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=845161E4-474C-44A9-92D4-1702748A3DA1@jonathanfoulkes.com \
    --to=jf@jonathanfoulkes.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=ippm@ietf.org \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=rpm@lists.bufferbloat.net \
    --cc=starlink@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