Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Amazon Leo announcing up to 1 Gbps (DOWN) and 400 Mbps (UP)
Date: Mon, 8 Dec 2025 20:26:03 -0500	[thread overview]
Message-ID: <b1b55489-980b-419d-b398-32b6391abe4e@rogers.com> (raw)
In-Reply-To: <rs617242-32n8-pq57-sp99-n882sp053s6q@ynat.uz>

Michael Richardson wrote:

>
>> One use case from northern canada that I'm aware is the 9am login at
>> government offices.  Lots of bandwidth needed to do all that 
>> ActiveDirectory
>> profile replication/update for all the people doing this at the same 
>> time.
>> I've heard stories of it taking an hour for everyone to get logged in.
>> AD replication ought to solve this, but apparently, it doesn't for 
>> reasons I
>> don't understand.

On 12/8/25 15:57, David Lang via Starlink wrote:
> microsoft protocols are not wan friendly, they do lots of round trips. 
> There are wan accelerator middle boxes that short-cut the protocols. 
> It's not just the AD lookups, it's filesystem queries as well. 

MS is really /really/ bad at handling anything bigger/more-laggy than 
the original token-ring and ethernet LANs. In the case of SMB, people 
built local caching/middleware boxes using Samba to get the RTT down.

They're the first folks who taught me that it's latency, not bandwidth.

--dave

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |              -- Mark Twain

  parent reply	other threads:[~2025-12-09  1:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-06 15:36 [Starlink] Amazon Leo announcing up to 1 Gbps (DOWN) and 400 Mbps (UP) Frantisek Borsik
2025-12-06 16:36 ` [Starlink] " J Pan
2025-12-06 23:58 ` David Lang
2025-12-07  0:02   ` Inemesit Affia
2025-12-07  0:08     ` David Lang
2025-12-08  4:31       ` Inemesit Affia
     [not found]         ` <5098.1765221714@obiwan.sandelman.ca>
2025-12-08 20:57           ` David Lang
     [not found]             ` <2609.1765228007@obiwan.sandelman.ca>
2025-12-08 21:15               ` David Lang
2025-12-08 21:22                 ` Michael Kan
2025-12-08 23:19                   ` Inemesit Affia
2025-12-08 23:20                     ` Inemesit Affia
2025-12-08 23:33                   ` David Lang
2025-12-09  1:26             ` David Collier-Brown [this message]
2025-12-09  7:49               ` Frantisek Borsik
2025-12-09  8:11                 ` Inemesit Affia
2025-12-09  8:23                   ` Frantisek Borsik
2025-12-09  8:21                     ` Inemesit Affia
2025-12-09  8:29                       ` Inemesit Affia
2025-12-09 21:53                         ` Frantisek Borsik
2025-12-10  1:06                           ` Nick Matthews
2025-12-10  1:24                             ` Frantisek Borsik
2025-12-10  1:45                               ` Joe Hamelin
2025-12-09 13:23       ` Livingood, Jason
2025-12-09 21:33         ` David Lang

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=b1b55489-980b-419d-b398-32b6391abe4e@rogers.com \
    --to=davec-b@rogers.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