From: Dave Taht <dave.taht@gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] the future of tcp - train wreck or evolution?
Date: Thu, 16 Jun 2022 09:39:29 -0700 [thread overview]
Message-ID: <CAA93jw5-8C0ngjHXQkRQzZbM-J9EH6=rUedGRsBDF5h1sLR42g@mail.gmail.com> (raw)
In-Reply-To: <580DF947-1160-405C-9019-0A6CD8FC49A3@ifi.uio.no>
On Wed, Jun 15, 2022 at 10:48 PM Michael Welzl <michawe@ifi.uio.no> wrote:
>
> … but I’m excited about slide 15 !
>
> "Heat, CO2, and radioactive waste are becoming measurable by-products of TCP inefficiency
> Fix TCP => Save the World!”
QUIC contributes 3x(?) more to global warming than TCP in these cases.
Btw, there's an interesting company attempting to put DCs underwater,
perhaps attached to old oil rigs or under windfarms, looking for their
first investment round, here, if you know anyone?
https://www.subseacloud.com/
I was a big jock cousteau fan back in the day.
Me, I've been mostly moving back to local applications, libreoffice is
a real joy compared to google docs, and I figure local apps are far,
far more power efficient than DCs are.
> People don’t yet focus enough on this - and it’s not only relevant in a data center context. See also:
>
> Michael Welzl: "Not a Trade-Off: On the Wi-Fi Energy Efficiency of Effective Internet Congestion Control", IEEE/IFIP WONS 2022, virtual, 30 March - 1 April 2022.
> Preprint: https://folk.universitetetioslo.no/michawe/research/publications/wons2022_authors_version.pdf
>
> A couple of IETFs ago, I did sign up to present something along these lines at an ICCRG meeting, but I asked late and got squeezed into an “if time permits” slot; some day in the future I’ll ask for a “proper slot” to elaborate on this.
>
> Cheers,
> Michael
>
>
>
> On Jun 16, 2022, at 4:35 AM, Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> as seen in 2008.
>
> https://slideplayer.com/slide/5747321/
>
> Regrettably all the answers on slide 13 are elided.
It was how clearly pugs saw things back then that was remarkable. I've
been really enjoying his twitter and blog ( https://akapugs.blog/)
lately. Also on a recent thread he pointed out this really excellent
computer history book:
https://twitter.com/aka_pugs/status/1537229947042820096
History does not repeat itself, but it rhymes.
>
>
> --
> FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2022-06-16 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 2:35 Dave Taht
2022-06-16 5:48 ` Michael Welzl
2022-06-16 7:22 ` Sebastian Moeller
2022-06-16 7:27 ` Michael Welzl
2022-06-16 16:39 ` Dave Taht [this message]
2022-06-16 20:23 ` Michael Welzl
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='CAA93jw5-8C0ngjHXQkRQzZbM-J9EH6=rUedGRsBDF5h1sLR42g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=michawe@ifi.uio.no \
/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