Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Luis A. Cornejo" <luis.a.cornejo@gmail.com>,
	libreqos <libreqos@lists.bufferbloat.net>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [LibreQoS] [Starlink] tarana strikes back
Date: Sun, 24 Sep 2023 13:37:34 -0700	[thread overview]
Message-ID: <CAA93jw6GuC_ghq_EeQVC0qfTrXGNjTwk=8FMmEXj35rSqPCyEw@mail.gmail.com> (raw)
In-Reply-To: <CAKJdXWCWxEFbZJ6u-=09UND5HwbZ=U3yXdQ4qjwU2Hp4XL8aXQ@mail.gmail.com>

That particular wisp so broadcasting their activities is deploying
"preseem" over tarana to manage their bufferbloat issues with great
success... although it would be nice if the tarana cpe uplink radio
had it more under control with a smaller fixed size buffer, at least,
and less retries in the mac. The right place to manage uplink
bufferbloat is at the uplink, not the central controller.

Everytime that wisp posts their tarana speedtest number, they show
300ms + buffering on the uplink side, which, while dramatically better
than 5g or starlink is still 10x too much.... and I pester them about
it. Sometimes they repost with the post-preseem number, sometimes not.
(preseem uses fq_codel).

The principal complaints about tarana are it is really, really
expensive, it uses up a lot of spectrum, and they have a lot more hype
than I would like.  Because the barrier to entry is so high, many
other alternatives may well be more cost-effective. I would certainly
like to see, touch, and test a setup myself! I like NLOS (non-line of
sight) technologies for incredibly difficult shots...

But:

My purpose in asking the list here was to ask if the analysis of cell
size was correct and reasonable (it certainly looked so to me), and
the economic argument that falls out of the resulting information
density seems compelling for designing hybrid fiber and wireless
networks of all sorts, not as an endorsement of tarana.

On Sun, Sep 24, 2023 at 1:19 PM Luis A. Cornejo
<luis.a.cornejo@gmail.com> wrote:
>
> Dave,
>
> Have you actually seen it in person? How is the bufferbloat situation? From the videos I've seen from WISPs and stuff Tarana shares on twitter it seems to be under control, but they seem very bandwidth oriented. A WISP (NextLink) seems to be deploying them, but it seems that is not near where I am. I inquired and they said I wasn't LOS to the tower. I responded back as to when they will deploy Tarana radios in my area and I got crickets.
>
> -Luis
>
> -Luis
>
> On Sat, Sep 23, 2023 at 9:34 PM Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
>>
>> Tarana, which is indeed, delivering one of the most amazing NLOS WISP
>> experiences I have ever seen,
>> just put out this white paper:
>>
>> https://www.taranawireless.com/a-comparison-of-next-generation-fwa-vs-leo-satellite/
>>
>> Can anyone question these Starlink numbers for cell size, etc?
>>
>> --
>> Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
>> Dave Täht CSO, LibreQos
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink



-- 
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos

       reply	other threads:[~2023-09-24 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw56+8qi_F6325rQeB8Lr-GivvvCB0hkR2019FXdbHw7Uw@mail.gmail.com>
     [not found] ` <CAKJdXWCWxEFbZJ6u-=09UND5HwbZ=U3yXdQ4qjwU2Hp4XL8aXQ@mail.gmail.com>
2023-09-24 20:37   ` Dave Taht [this message]
2023-09-25  8:11     ` David Lang
2023-09-26 18:37       ` [LibreQoS] [Starlink] Starlink cell capacity (was; tarana strikes back) Jim Forster
2023-09-26 19:00         ` David Lang
2023-09-26 23:05           ` dan

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

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

  git send-email \
    --in-reply-to='CAA93jw6GuC_ghq_EeQVC0qfTrXGNjTwk=8FMmEXj35rSqPCyEw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=luis.a.cornejo@gmail.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