From: Nathan Owens <nathan@nathan.io>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Apple WWDC Talks on Latency/Bufferbloat
Date: Fri, 11 Jun 2021 12:14:08 -0700 [thread overview]
Message-ID: <CALjsLJvLkV+VJY5OuThZZMZWdkx6iCWxAiNOoQ_0y5OfBKyqyA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
Some relevant talks / publicity at WWDC -- the first mentioning CoDel,
queueing, etc. Featuring Stuart Cheshire. iOS 15 adds a developer test for
loaded latency, reported in "RPM" or round-trips per minute.
I ran it on my machine:
nowens@mac1015 ~ % /usr/bin/networkQuality
==== SUMMARY ====
Upload capacity: 90.867 Mbps
Download capacity: 93.616 Mbps
Upload flows: 16
Download flows: 20
Responsiveness: Medium (840 RPM)
Reduce network delays for your app
https://developer.apple.com/videos/play/wwdc2021/10239/
CPU performance and network throughput rates keep improving, but the speed
of light is one limit that isn't going any higher. Learn the APIs and best
practices to maximize your app's responsiveness and efficiency by keeping
network round-trip times low and minimizing the number of round trips when
performing network operations.
Optimize for 5G networks
https://developer.apple.com/videos/play/wwdc2021/10103/
5G enables new opportunities for your app or game through better
performance for data transfer, higher bandwidth, lower latency, and much
more. Discover how you can take advantage of the latest networking
technology and Apple hardware to create adaptive experiences for your
content that best suit someone's data connection and optimize network
traffic.
Accelerate networking with HTTP/3 and QUIC
https://developer.apple.com/videos/play/wwdc2021/10094/
The web is changing, and the next major version of HTTP is here. Learn how
HTTP/3 reduces latency and improves reliability for your app and discover
how its underlying transport, QUIC, unlocks new innovations in your own
custom protocols using new transport functionality and multi-streaming
connection groups
[-- Attachment #2: Type: text/html, Size: 2185 bytes --]
next reply other threads:[~2021-06-11 19:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 19:14 Nathan Owens [this message]
2021-06-11 21:58 ` Jonathan Morton
2021-06-12 16:11 Rich Brown
2021-06-17 18:16 ` Matt Mathis
2021-06-17 23:43 ` Christoph Paasch
2021-06-18 0:17 ` Matt Mathis
2021-06-18 1:03 ` Christoph Paasch
2021-06-18 3:33 ` Matt Mathis
2021-06-28 22:54 ` Christoph Paasch
2021-06-29 7:58 ` Sebastian Moeller
2021-07-06 18:54 ` Christoph Paasch
2021-07-06 19:08 ` 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/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=CALjsLJvLkV+VJY5OuThZZMZWdkx6iCWxAiNOoQ_0y5OfBKyqyA@mail.gmail.com \
--to=nathan@nathan.io \
--cc=bloat@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