From: Jonathan Morton <chromatix99@gmail.com>
To: "David P. Reed" <dpreed@reed.com>
Cc: "Dave Täht" <dave@taht.net>, bloat <bloat@lists.bufferbloat.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] DC behaviors today
Date: Wed, 13 Dec 2017 01:20:02 +0200 [thread overview]
Message-ID: <CAJq5cE2aj6JLnUWO+Wyp2xbOMaomvNojYE4zEnGvtfpwXrYOmg@mail.gmail.com> (raw)
In-Reply-To: <1513119230.638732339@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
This is also true in the consumer space, and is the reason why ISPs can
save money by taking advantage of statistical multiplexing. On average, I
personally could be satisfied with a megabit, but it's a real pain to
download gigabyte-class software updates at that speed.
If it takes me literally days to download a game's beta versions, any
comments I might have will be stale by the time they can be heard, and in
the meantime my other uses of the internet have been seriously impaired.
It's much more useful if I can download the same data in an hour, and spend
the remaining time evaluating. So throughput is indeed a factor in
response time, once the size of the response is sufficiently large.
Occasionally, of course, practically everyone in the country wants to tune
into coverage of some event at the same time. More commonly, they simply
get home from work and school at the same time every day. That breaks the
assumptions behind pure statistical multiplexing, and requires a greater
provisioning factor.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 1135 bytes --]
next prev parent reply other threads:[~2017-12-12 23:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw43M=dhPOFhMJo7f-qOq=k=kKS6ppq4o9=hsTEKoBdUpA@mail.gmail.com>
[not found] ` <92906bd8-7bad-945d-83c8-a2f9598aac2c@lackof.org>
[not found] ` <CAA93jw5pRMcZmZQmRwSi_1dETEjTHhmg2iJ3A-ijuOMi+mg4+Q@mail.gmail.com>
[not found] ` <CAKiAkGT54RPLQ4f1tzCj9wcW=mnK7+=uJfaotw9G+H_JEy_hqQ@mail.gmail.com>
2017-12-04 4:19 ` [Bloat] " Dave Taht
2017-12-04 9:13 ` [Bloat] [Cerowrt-devel] " Mikael Abrahamsson
2017-12-04 9:31 ` Joel Wirāmu Pauling
2017-12-04 10:18 ` Mikael Abrahamsson
2017-12-04 10:27 ` Joel Wirāmu Pauling
2017-12-04 10:43 ` Pedro Tumusok
2017-12-04 10:47 ` Joel Wirāmu Pauling
2017-12-04 10:57 ` Pedro Tumusok
2017-12-04 10:59 ` Joel Wirāmu Pauling
2017-12-04 12:44 ` Mikael Abrahamsson
2017-12-04 19:59 ` dpreed
2017-12-04 20:29 ` David Collier-Brown
2017-12-08 7:05 ` Mikael Abrahamsson
2017-12-12 15:09 ` Luca Muscariello
2017-12-12 18:36 ` Dave Taht
2017-12-12 22:53 ` dpreed
2017-12-12 23:20 ` Jonathan Morton [this message]
2017-12-13 10:20 ` Mikael Abrahamsson
2017-12-13 10:45 ` Luca Muscariello
2017-12-13 15:26 ` Neil Davies
2017-12-13 16:41 ` Jonathan Morton
2017-12-13 18:08 ` dpreed
2017-12-13 19:55 ` Neil Davies
2017-12-13 21:06 ` Jonathan Morton
2017-12-14 8:22 ` Mikael Abrahamsson
2017-12-17 21:37 ` Benjamin Cronce
2017-12-18 8:11 ` Mikael Abrahamsson
2017-12-17 11:52 ` Matthias Tafelmeier
2017-12-18 7:50 ` Mikael Abrahamsson
2017-12-19 17:55 ` Matthias Tafelmeier
2017-12-27 15:15 ` Matthias Tafelmeier
2018-01-20 11:55 ` Joel Wirāmu Pauling
2017-12-04 12:41 ` Mikael Abrahamsson
2017-12-04 10:56 ` [Bloat] Linux network is damn fast, need more use XDP (Was: DC behaviors today) Jesper Dangaard Brouer
2017-12-04 17:00 ` Dave Taht
2017-12-04 20:49 ` Joel Wirāmu Pauling
2017-12-07 8:43 ` Jesper Dangaard Brouer
2017-12-07 8:49 ` Jesper Dangaard Brouer
2017-12-04 17:19 ` Matthias Tafelmeier
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=CAJq5cE2aj6JLnUWO+Wyp2xbOMaomvNojYE4zEnGvtfpwXrYOmg@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=dpreed@reed.com \
/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