From: Juliusz Chroboczek <jch@irif.fr>
To: "Bjørn Ivar Teigen" <bjorn@domos.no>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Finite-Buffer M/G/1 Queues with Time and Space Priorities
Date: Sat, 30 Jul 2022 14:55:38 +0200 [thread overview]
Message-ID: <87czdmwyid.wl-jch@irif.fr> (raw)
In-Reply-To: <CAKf5G6K+xgOmDwiASefpmT=Kmikj6ZHvJX6TwAu4sXggXNoQ0g@mail.gmail.com>
> I've got a pet theory that the burstiness of internet traffic is an artifact of
> the fact that academics and marketing departments, in a weird kind of unholy
> alliance, keep focusing on peak throughput.
Hmm.
Packet pacing is counterintuitive and tricky to get right. It's highly
counter-intuitive to most people that delaying packet transmission will
end up reducing latency. It's tricky to decide how to pace your packets
when you don't know (1) how your congestion window is going to evolve and
(2) how the application demand is going to evolve in the near future. Let
alone that it reduces cache locality and requires fine-grained timers,
both of which are costly if implemented in software on a general-purpose
OS.
As to academics having sold out to marketing departments -- it seems I've
missed out, where do I collect my share?
-- Juliusz
next prev parent reply other threads:[~2022-07-30 12:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.461.1659002134.1281.starlink@lists.bufferbloat.net>
2022-07-29 19:38 ` David P. Reed
2022-07-29 20:34 ` Bjørn Ivar Teigen
2022-07-30 12:55 ` Juliusz Chroboczek [this message]
2022-07-30 16:17 ` David Lang
2022-07-29 20:36 ` Bless, Roland (TM)
2022-07-31 11:58 ` Sebastian Moeller
2022-07-31 20:22 ` David P. Reed
2022-07-27 15:34 Dave Taht
2022-07-27 17:23 ` Luca Muscariello
2022-07-28 8:45 ` Bless, Roland (TM)
2022-07-28 9:26 ` Bjørn Ivar Teigen
2022-07-28 9:55 ` Sebastian Moeller
2022-07-28 10:16 ` Bjørn Ivar Teigen
2022-07-28 13:50 ` Dave Taht
2022-07-29 14:55 ` Dave Taht
2022-07-29 15:29 ` Sebastian Moeller
2022-07-29 15:29 ` Sebastian Moeller
2022-07-29 17:08 ` Dave Taht
2022-07-29 17:41 ` Sebastian Moeller
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=87czdmwyid.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=bjorn@domos.no \
--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