From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net, Dave Taht <dave.taht@gmail.com>
Subject: [Bloat] Sidebar on s-curves
Date: Thu, 27 Oct 2016 13:56:00 -0400 [thread overview]
Message-ID: <43e779f2-5bff-ad4c-8e7f-6b339a7f0123@rogers.com> (raw)
In-Reply-To: <CAA93jw7ret3FGXG=QxweHB+5XZiwmuzOuoyRgm6jSLpBtyGhZw@mail.gmail.com>
On 27/10/16 12:56 PM, Dave Taht wrote:
> When you are on one side of an S curve, it's hard to see where it flattens out.
>
> I've been meaning to research and write a piece called "have we
> reached 'Peak Bandwidth'"? for a while now.
>
> My thesis is that what users actually want is short RTTs for
> interactive, once basic bandwidth needs are slaked, which starts to
> happen once you crack the largest typical load (which these days is 4k
> video streaming).
>
> gbit fiber is *way* on the unneeded side of the demand curve for home users.
>
It's not an s-curve, but Neil Gunther had done some very interesting
work on load/throughput curves, specifically including predicting the
drop-off after reaching 100%. Look for the Universal Scalability Law.
http://www.perfdynamics.com/Manifesto/USLscalability.html
I suspect it might be a variant of the same problem.
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
next prev parent reply other threads:[~2016-10-27 17:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 21:56 [Bloat] 22 seconds til bloat on gfiber? Dave Taht
2016-10-22 23:52 ` Jonathan Morton
2016-10-23 1:33 ` jb
2016-10-23 1:45 ` Dave Taht
2016-10-23 1:47 ` Dave Taht
2016-10-23 2:27 ` jb
[not found] ` <CAJq5cE3DsV9v6ATVeq+vF_kVFjKy+8Qjwe-P01ZZbyKZB9HC6w@mail.gmail.com>
2016-10-23 8:29 ` Jonathan Morton
2016-10-23 9:23 ` jb
2016-10-23 16:14 ` Klatsky, Carl
2016-10-24 0:46 ` jb
2016-10-24 13:13 ` Klatsky, Carl
2016-10-24 16:11 ` Noah Causin
2016-10-24 20:27 ` Klatsky, Carl
2016-10-23 2:30 ` Benjamin Cronce
2016-10-25 7:10 ` Jonas Mårtensson
2016-10-23 5:50 ` Mikael Abrahamsson
2016-10-24 16:57 ` Jonas Mårtensson
2016-10-24 22:10 ` Benjamin Cronce
2016-10-25 0:09 ` jb
2016-10-25 12:01 ` Benjamin Cronce
2016-10-25 13:11 ` Klatsky, Carl
2016-10-25 21:20 ` jb
2016-10-26 0:02 ` Klatsky, Carl
2016-10-25 15:59 ` Jan Ceuleers
2016-10-26 1:05 ` Benjamin Cronce
2016-10-26 14:49 ` Jan Ceuleers
2016-10-26 15:36 ` Mikael Abrahamsson
2016-10-27 14:32 ` Jonas Mårtensson
2016-10-27 16:56 ` Dave Taht
2016-10-27 17:56 ` David Collier-Brown [this message]
2016-10-27 19:30 ` David Lang
2016-10-27 19:41 ` Dave Taht
2016-10-27 19:48 ` Aaron Wood
2016-10-28 15:51 ` Jan Ceuleers
2016-10-28 15:55 ` Klatsky, Carl
2016-10-27 19:45 ` Aaron Wood
2016-10-27 20:17 ` Mikael Abrahamsson
2016-12-07 5:40 ` Jonathan Morton
2016-12-07 7:05 ` Mikael Abrahamsson
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=43e779f2-5bff-ad4c-8e7f-6b339a7f0123@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=davecb@spamcop.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