General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>
Cc: dfk@eecs.berkeley.edu, dghosal@ucdavis.edu,
	chapmanm@eecs.berkeley.edu,  mkfarrens@ucdavis.edu,
	tomlin@eecs.berkeley.edu, nhanford@ucdavis.edu
Subject: [Bloat] pacing, applied differently than bbr
Date: Sat, 8 Feb 2020 23:11:54 -0800	[thread overview]
Message-ID: <CAA93jw6FQb7ES-ZuFWfsM=FncCG7cwjZ5O-18uaCYystt8YSEg@mail.gmail.com> (raw)

I don't know how I stumbled across this, but it seemed interesting at
this late hour. I wonder if they kept at it or tried ecn also.

"A Model Predictive Control Approach to Flow Pacing for TCP"

"we propose a different approach to latency based congestion control.
In particular, our controller sets the maximum pacing rate by solving
a model-based receding horizon control problem at each time step. Each
new roundtrip time (RTT) measurement is first incorporated into a
linear time-varying (LTV) predictive model. Subsequently, we solve a
one-step look-ahead optimization problem which finds the pacing rate
which optimally trades off RTT, RTT variance, and throughput according
to the most recent model. Our method is computationally inexpensive
making it readily implementable on current systems."

https://people.eecs.berkeley.edu/~dfk/pdfs/network_control_camera_ready.pdf


-- 
Make Music, Not War

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729

             reply	other threads:[~2020-02-09  7:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09  7:11 Dave Taht [this message]
2020-02-09 16:39 ` Taran Lynn
2020-02-26  6:51   ` Taran Lynn
2020-02-26 20:12     ` Dave Taht
2020-03-04  8:49       ` Taran Lynn
2020-02-26 21:00     ` Jonathan Morton
2020-02-09 18:21 ` David Fridovich-Keil

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

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

  git send-email \
    --in-reply-to='CAA93jw6FQb7ES-ZuFWfsM=FncCG7cwjZ5O-18uaCYystt8YSEg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chapmanm@eecs.berkeley.edu \
    --cc=dfk@eecs.berkeley.edu \
    --cc=dghosal@ucdavis.edu \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=mkfarrens@ucdavis.edu \
    --cc=nhanford@ucdavis.edu \
    --cc=tomlin@eecs.berkeley.edu \
    /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