Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: David Lang <david@lang.hm>
Cc: Mike Puchol <mike@starlink.sx>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] 69,000 Users
Date: Wed, 30 Jun 2021 00:51:04 -0700	[thread overview]
Message-ID: <7DFC1294-FC14-44DF-B28B-FFB89E0BDF4E@teklibre.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2106300025020.3753340@qynat-yncgbc>

While I agree that big money is in backhaul...

My take on how to turn a per-user profit was easy. Just increase the user density and user side always offer the lowest latency possible from LEO. 

I would hate to be quoted on this out of context, but 50Mbit ought to be enough for everyone. Web traffic in particular is almost entirely bound by RTT [1]. There’s a lot of studies showing this. I keep looking for the key google one with no luck….

You can’t use up 50Mbit in your typical 3sec web page load before it ends. 

Designing a network for speedtest is silly. (admittedly convincing the world that speedtest is the worlds most misleading benchmark is hard) 

Designing a new network for real applications like voip, videoconferencing, email, chat, and 4k video streaming is much easier if you always retain consistently low latency.

Many the headaches and hassle in scheduling a bunch of spot beams go away if you just target real applications, with good queue management, and a deep knowledge of how our network protocols actually work. 

There’s plenty that could be done at the l2 layer to increase density also.  "Music is the space between the notes” - said Debussy

[1] With *really good queue management* at the head end, and an e2e approach to improving the browsers, we (teklibre) long ago proved how to improve PLT enormously at large RTTs.

> On Jun 30, 2021, at 12:30 AM, David Lang <david@lang.hm> wrote:
> 
> they have FCC approval for 1m customer terminals in the US, and have asked to increase that due to demonstrated demand (to something like 5m terminals)
> 
> 500k customers is not nearly the break-even point, but that's still a lot of equipment deployed and supported.
> 
> I suspect that they will be more limited by the number of stations they can build than the interest from customers. As user density increases, they will need to launch more satellites, but as Starship comes online, the cost to do so will drop significantly.
> 
> the orbital life of a satellite may end up being a bit better than you think, they will de-orbit by themselves after about 5 years, but they do have thrusters that they can use to raise their orbits to extend their lives if they don't need the fuel for collision avoidance.
> 
> David Lang
> 
> On Wed, 30 Jun 2021, Mike Puchol wrote:
> 
>> Date: Wed, 30 Jun 2021 09:23:02 +0200
>> From: Mike Puchol <mike@starlink.sx>
>> To: David Lang <david@lang.hm>, Dave Taht <dave.taht@gmail.com>
>> Cc: starlink@lists.bufferbloat.net
>> Subject: Re: [Starlink] 69,000 Users
>> 500k customers is ~$600m in gross revenue per year. Assuming no operating costs, takes, etc., $10bn takes ~16 years to pay back. They need to add way more customers onto that investment.
>> 
>> In traditional land-based telcos, it is frequent to split the backbone and customer sides, having a “TowerCo” with all the expensive infrastructure, that has a payback period of 25 years, and “CustomerCo” where payback needs to be 12-18 months. In Starlink’s case, unless they cannot increase satellite lifespan, and/or make them very cheap, the payback period is fixed at 5 years. For gateways and ground infrastructure, you can stretch it to compensate, but you cannot justify, say, a 50 year payback.
>> 
>> IMHO the direct to customer side will end up being residual, high price for those who really need it, and their revenue will come from backhauling mobile and FTTH operators, airlines, cruises, and the military.
>> 
>> Best,
>> 
>> Mike
>> On Jun 30, 2021, 7:48 AM +0200, Dave Taht <dave.taht@gmail.com>, wrote:
>>> On Tue, Jun 29, 2021 at 10:24 PM David Lang <david@lang.hm> wrote:
>>>> 
>>>> I think that was 69k simultanious users
>>>> 
>>>> dishy production cost is currently down to ~$1k/unit (I've heard that it was
>>>> ~$3k/unit for the first ones)
>>> 
>>> Keep hoping they will add good, nay, great!! queue management.
>>> Software costs nothing in qty.
>>> 
>>>> But the long term upside if they can pull it off is a license to print money,
>>>> I've seen speculation that it's on the order of 30B/year when fully built
>>> 
>>> I think that's kind of doable.
>>> 
>>> It's too bad all those users are behind a CGN and cannot talk to each
>>> other, routing calls at least from one village to another would stay
>>> on the same sat.
>>> 
>>>> 
>>>> David Lang
>>>> 
>>>> On Tue, 29 Jun 2021, Daniel AJ Sokolov wrote:
>>>> 
>>>>> Date: Tue, 29 Jun 2021 19:00:32 -0700
>>>>> From: Daniel AJ Sokolov <daniel@sokolov.eu.org>
>>>>> To: starlink@lists.bufferbloat.net
>>>>> Subject: [Starlink] 69,000 Users
>>>>> 
>>>>> Starlink currently has 69,000 User, according to what Elon Musk said
>>>>> today at the Mobile World Congress in Barcelona.
>>>>> 
>>>>> In a year, he wants to have 500,000 users.
>>>>> 
>>>>> He expects having to invest 25 to 30 billion US-Dollars to fully build
>>>>> Starlink.
>>>>> 
>>>>> Each Dishy costs Starlink about double the current purchase price.
>>>>> However, they want to reduce the production cost to "a few hundred
>>>>> dollars" - which is why they are working on their own factory in Texas.
>>>>> 
>>>>> FYI
>>>>> Daniel
>>>>> 
>>>>> _______________________________________________
>>>>> 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
>>> 
>>> 
>>> 
>>> --
>>> Latest Podcast:
>>> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>>> 
>>> Dave Täht CTO, TekLibre, LLC
>>> _______________________________________________
>>> 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


  parent reply	other threads:[~2021-06-30  7:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  2:00 Daniel AJ Sokolov
2021-06-30  5:24 ` David Lang
2021-06-30  5:48   ` Dave Taht
2021-06-30  7:13     ` [Starlink] routing capability in starlinks Dave Taht
2021-06-30 14:43       ` Michael Richardson
2021-06-30 23:56         ` Nick Buraglio
2021-06-30  7:23     ` [Starlink] 69,000 Users Mike Puchol
2021-06-30  7:30       ` David Lang
2021-06-30  7:43         ` Mike Puchol
2021-06-30  7:51         ` Dave Taht [this message]
2021-06-30  9:57         ` Mikael Abrahamsson
2021-06-30 14:24           ` Dave Taht
2021-06-30 18:33             ` Mikael Abrahamsson
2021-06-30 20:40               ` Dick Roy
2021-06-30 23:33         ` Daniel AJ Sokolov
2021-07-01  0:00           ` David Lang
2021-07-01  0:03             ` Daniel AJ Sokolov
2021-07-01  0:20               ` David Lang
2021-06-30 10:53       ` Jared Mauch

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=7DFC1294-FC14-44DF-B28B-FFB89E0BDF4E@teklibre.net \
    --to=davet@teklibre.net \
    --cc=david@lang.hm \
    --cc=mike@starlink.sx \
    --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