Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Doc Searls <doc@searls.com>
To: Starlink-Bufferbloat <starlink@lists.bufferbloat.net>
Subject: [Starlink] Widely different bufferbloat on two machines connected to one access point
Date: Tue, 17 Jan 2023 08:27:04 -0800	[thread overview]
Message-ID: <35DD8C11-8E9B-4E5B-B6F8-F3496511EBCC@searls.com> (raw)

A question for the true geniuses here, before I call an Apple one who isn't...

We have two laptops here, both feet away from the nearest Eero hot spot in a household network fed by a cable modem, an Aris DOCSIS 3.1 router and a 24-port Netgear switch.

My laptop is a 6-year old MacBook Pro. My wife's laptop is a brand new MacBook Air that rocks in every respect but its network connection,

Using Fast.com, I'm getting 450 Mbps down, 38 Mbps up, with 14 ms of unloaded latency and 28 ms of loaded latency. My wife is getting 67 Mbps down, 28 Mbps up, 15 ms of unloaded latency and 780 ms of loaded latency. 

Repeated tests yield similar results.

In other words, her machine is getting a lot of bufferbloat and mine is not.

If I connect by Ethernet direct to the switch through a USB-C to Ethernet adapter, I get 880 Mbps down, with other values about the same. Using the same Ethernet connection, she gets roughly the same results as she gets on WiFi.

So it seems the problem is with her new machine. If so, what's the fix?

We do have an immediate need: downloading seven years of emails via IMAP from her server at Rackspace, which we are leaving because the company failed spectacularly in a ransomware attack and is unworthy of customer faith. It has taken most of a week so far to download 390,000 emails, and we would like to speed that up.

I'm less lucky, since my mail (unlike hers) was on the Rackspace Exchange server, which was the target of the attack. I have been unable to retrieve anything so far, and I am losing hope that I ever will.

Anyway, the question is about radically different bufferbloat on two machines connected the same way—and what to do about it.

Thanks,

Doc

             reply	other threads:[~2023-01-17 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 16:27 Doc Searls [this message]
2023-01-17 16:48 ` Dave Taht
2023-01-17 18:25   ` Ben Greear

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=35DD8C11-8E9B-4E5B-B6F8-F3496511EBCC@searls.com \
    --to=doc@searls.com \
    --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