Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Hesham ElBakoury <helbakoury@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] SIGCOMM MIT paper: Starvation in e2e congestion control
Date: Thu, 11 Aug 2022 07:29:29 -0700	[thread overview]
Message-ID: <30146b25-b043-a2d8-c7b4-12b9df9caab1@gmail.com> (raw)
In-Reply-To: <1659994794.324713695@apps.rackspace.com>

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

Hi David,

I think someone such as Professor Hari who got many awards including the 
sigcomm 2021 life-achievement award or his student Venkat need to be 
educated on Fair Queuing. There are many publications and text books 
which describe FQ. The results of this paper is for network paths that 
do not use FQ or ECN. Venkat/Hari can provide more details.

For the CAP theorem, do you think I can get C,A,P, if this is what I 
need ? if this is the case, then this theorem is wrong or has limited 
applicability, correct ?

Thanks

Hesham

On 8/8/2022 2:39 PM, David P. Reed via Starlink wrote:
>
> Two things:
>
> 1) Do they understand Fair Queuing among flows? I actually doubt it or 
> they would have commented on it, to be intellectually honest.
>
> But maybe they will publish another paper that includes that? I get 
> really frustrated when reviewers don't force papers to address 
> well-known contradictory evidence. What are reviewers and referees who 
> are expert in the field for if not that? (my crankiness is justified, 
> I believe, by my commitment to research quality. But hey, maybe MIT 
> CSAIL faculty and SIGCOMM don't care about quality? Or maybe there's 
> been nothing published about FQ?
>
> 2) I absolutely hate folks who invent "theorems" that say you can have 
> "any two of three" properties. It's become popular in computer systems 
> research, but it actually creates a huge intellectual mess.
>
> The CAP theorem, for example has some very peculiar definitions in 
> order to make C, A, and P "independent" axes. Of course they are NOT 
> independent in engineering practice. In fact, they aren't even 
> "binary" - there's no "yes" or "no" to C, A or P - they are not even 
> spectra that map to some increasing sequence.
>
> Yes, you can't always get what you want. But you can almost always get 
> what you need, and that is never a specific two out of three.
>
> Especially not in queue management algorithms.
>
> Goddamn cutesy anti-intellectuals.
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

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

  parent reply	other threads:[~2022-08-11 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3.1659715201.24001.starlink@lists.bufferbloat.net>
2022-08-08 21:39 ` David P. Reed
2022-08-08 22:37   ` David Lang
2022-08-08 22:41     ` Dave Taht
2022-08-11 14:29   ` Hesham ElBakoury [this message]
2022-08-17 21:34   ` Dave Taht
     [not found] <mailman.562.1660228174.1281.starlink@lists.bufferbloat.net>
2022-08-11 19:34 ` David P. Reed
2022-08-11 20:22   ` Ulrich Speidel
2022-08-11 20:24     ` Ulrich Speidel
2022-08-12 14:21   ` Livingood, Jason
2022-08-12 14:23     ` Hesham ElBakoury
2022-08-25 20:26   ` Dave Taht
2022-08-04 19:05 Dave Taht
2022-08-07  4:28 ` Venkat Arun

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=30146b25-b043-a2d8-c7b4-12b9df9caab1@gmail.com \
    --to=helbakoury@gmail.com \
    --cc=dpreed@deepplum.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