Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: rjmcmahon <rjmcmahon@rjmcmahon.com>,
	rjmcmahon via Make-wifi-fast
	<make-wifi-fast@lists.bufferbloat.net>,
	Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	libreqos <libreqos@lists.bufferbloat.net>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] [Make-wifi-fast] [Rpm] make-wifi-fast 2016 & crusader
Date: Wed, 07 Dec 2022 08:50:13 +0100	[thread overview]
Message-ID: <566AC2D7-FB33-4924-9B21-BE9A8476E0B3@gmx.de> (raw)
In-Reply-To: <a6e57a3ac0e51e200313da11f7e5059d@rjmcmahon.com>

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

Hi Bob,

What simple end users would need is (semi-)public iperf2 servers accessible over the internet to be comparably easy to use as iperf3....

Regards
        Sebastian

On 6 December 2022 18:46:18 CET, rjmcmahon via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net> wrote:
>Nice write up and work over the years.
>
>On tooling:
>
>iperf 2 supports full duplex, multiple parallel streams, tx start times, bounceback, isochronous, etc. Man page is here
>
>https://iperf2.sourceforge.io/iperf-manpage.html
>
>The flows code in the flows directory
>
>https://sourceforge.net/p/iperf2/code/ci/master/tree/flows/
>
>is written in python 3 and leverages asyncio.
>
>https://docs.python.org/3/library/asyncio.html
>
>This is all released as open source.
>
>Bob
>> This is where things stood on the wifi front, back in 2016. Nobody
>> understood us...
>> 
>> https://docs.google.com/document/d/1Se36svYE1Uzpppe1HWnEyat_sAGghB3kE285LElJBW4/edit#
>> 
>> So I sort of enjoyed re-reading that this morning, and all the
>> enthusiastic commentary we'd had on it. Perhaps we can reshape it and
>> find ways to move forward today?
>> 
>> I am happy to have seen so many products hitting the market 5+ years
>> later that leverage this work, many openwrt derived, like evenroute,
>> quantum, and openwifi, others from pure linux, like eero and google
>> fiber, and so far as I can tell, in many a chromebook, and of course
>> ios and osx.
>> 
>> Still, there was so much work left to be done, and the work applied to
>> all forms of wireless technology, be it 6 or 12ghz, or 60ghz, or
>> starlink. Just the other day I was watching a 5G engineer that was
>> struggling to get decent simultaneous throughput up and down, the test
>> tool showing that, but not the 25 seconds of buffering built into the
>> rmnet driver in poor conditions, and "only" 150ms perfect ones. This
>> test tool shows "perfect" throughput for this device:
>> 
>> https://www.spinics.net/lists/netdev/msg865852.html
>> (anyone know which tool it was? see image here:
>> https://drive.google.com/file/d/1gSbozrtd9h0X63i6vdkNpN68d-9sg8f9/view
>> )
>> 
>> vs the actual, underlying, unusable 25 seconds!!! - result - if only
>> that test tool attempted to start up even one more flow partially
>> through the test, perhaps we'd be getting somewhere. An increasingly
>> favorite test of mine is the staggered start "squarewave" tests in the
>> flent suite. For those that haven't tried it, crusader is the first
>> tool I've seen that not only has a staggered start latency under load
>> test, but as its written in rust, runs on every OS in the planet. Give
>> it a shot?
>> 
>> https://github.com/Zoxc/crusader/releases/tag/v0.0.9-testing
>> 
>> _______________________________________________
>> Rpm mailing list
>> Rpm@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/rpm
>_______________________________________________
>Make-wifi-fast mailing list
>Make-wifi-fast@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/make-wifi-fast
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 4139 bytes --]

  reply	other threads:[~2022-12-07  7:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 15:59 [Starlink] " Dave Taht
2022-12-06 17:46 ` [Starlink] [Rpm] " rjmcmahon
2022-12-07  7:50   ` Sebastian Moeller [this message]
2022-12-07 19:28     ` [Starlink] [Make-wifi-fast] " rjmcmahon

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/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=566AC2D7-FB33-4924-9B21-BE9A8476E0B3@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=rjmcmahon@rjmcmahon.com \
    --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