From: Dave Taht <dave.taht@gmail.com> To: bloat <bloat@lists.bufferbloat.net>, codel@lists.bufferbloat.net, ECN-Sane <ecn-sane@lists.bufferbloat.net>, Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>, flent-users <flent-users@flent.org>, BBR Development <bbr-dev@googlegroups.com> Cc: ghosal@cs.ucdavis.edu, tflynn@ucdavis.edu Subject: [Flent-users] D* tcp looks pretty good, on paper Date: Thu, 7 Jan 2021 10:35:00 -0800 [thread overview] Message-ID: <CAA93jw6qczFKudMt3kzmGzRmCvgoemBta69AoENX3oCtR+CnYw@mail.gmail.com> (raw) See: https://arxiv.org/pdf/2012.14996.pdf Things I really like: * they used flent * Using "variance" as the principal signal. This is essentially one of the great unpublished and unanalyzed improvements on the minstrel algorithm as well * Conventional ecn response * outperforms bbr on variable links Only negative so far is I haven't found any published source to it. :( Otherwise a very promising start to a year. "The choice of feedback mechanism between delay and packet loss has long been a point of contention in TCP congestion control. This has partly been resolved, as it has become increasingly evident that delay based methods are needed to facilitate modern interactive web applications. However, what has not been resolved is what control should be used, with the two candidates being the congestion window and the pacing rate. BBR is a new delay based congestion control algorithm that uses a pacing rate as its primary control and the congestion window as a secondary control. We propose that a congestion window first algorithm might give more desirable performance characteristics in situations where latency must be minimized even at the expense of some loss in throughput. To evaluate this hypothesis we introduce a new congestion control algorithm called TCP D*, which is a congestion window first algorithm that adopts BBR's approach of maximizing delivery rate while minimizing latency. In this paper, we discuss the key features of this algorithm, discuss the differences and similarity to BBR, and present some preliminary results based on a real implementation." -- "For a successful technology, reality must take precedence over public relations, for Mother Nature cannot be fooled" - Richard Feynman dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next reply other threads:[~2021-01-07 18:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-07 18:35 Dave Taht [this message] 2021-01-07 19:20 ` [Flent-users] " Taran Lynn 2021-01-07 20:25 ` [Flent-users] Re: [Make-wifi-fast] " Bob McMahon 2021-01-07 21:41 ` Dave Taht 2021-01-07 22:22 ` Bob McMahon 2021-01-08 14:35 ` [Flent-users] Re: [Ecn-sane] " Rodney W. Grimes 2021-01-08 17:52 ` Bob McMahon 2021-01-08 15:38 ` [Flent-users] Re: [bbr-dev] " Neal Cardwell 2021-01-08 16:13 ` [Flent-users] Re: [Make-wifi-fast] " Jonathan Morton 2021-01-08 16:24 ` Bryson Richard
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.flent.org/postorius/lists/flent-users.flent.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAA93jw6qczFKudMt3kzmGzRmCvgoemBta69AoENX3oCtR+CnYw@mail.gmail.com \ --to=dave.taht@gmail.com \ --cc=bbr-dev@googlegroups.com \ --cc=bloat@lists.bufferbloat.net \ --cc=codel@lists.bufferbloat.net \ --cc=ecn-sane@lists.bufferbloat.net \ --cc=flent-users@flent.org \ --cc=ghosal@cs.ucdavis.edu \ --cc=make-wifi-fast@lists.bufferbloat.net \ --cc=tflynn@ucdavis.edu \ --subject='Re: [Flent-users] D* tcp looks pretty good, on paper' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox