From: "Livingood, Jason" <jason_livingood@comcast.com>
To: "Jeremy Austin" <jeremy@aterlo.com>,
"Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] [EXTERNAL] Re: FCC NOI due dec 1 on broadband speed standards
Date: Tue, 14 Nov 2023 18:34:57 +0000 [thread overview]
Message-ID: <CCB5B6B9-8CB7-4952-ACFA-485147220762@comcast.com> (raw)
In-Reply-To: <CACw=56KRvQK4t6dKUKYKH-+FgYErdB4YcMWAN=e34Fi2dvtVfw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 845 bytes --]
> That's an unusually high ratio of up to down, so my suspicion is that they aren't time correlated; they're also not /normal/ or /evening/ peaks, I'm expecting.
I suspect the higher upstream is due to the fact that (using the Meetecho tool) each WG session is streaming live A/V to the internet (and remote and in-person participants are logged into that as well).
[A graph showing a line of yellow and green lines Description automatically generated]
> There's a big difference between individual peaks of upload and aggregate peaks of upload; most people aren't streaming high symmetric bandwidth simultaneously. Consequently a peak busy hour online load, I'm finding, is still much more like 8:1 over all users (idle and active), in Preseem's data set.
That ratio sounds much more typical, for sure.
Jason
[-- Attachment #1.2: Type: text/html, Size: 5195 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 200022 bytes --]
prev parent reply other threads:[~2023-11-14 18:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 16:32 [NNagain] " Dave Taht
2023-11-11 18:24 ` rjmcmahon
2023-11-14 15:46 ` Livingood, Jason
2023-11-14 16:06 ` Dave Taht
2023-11-14 16:14 ` Frantisek Borsik
2023-11-14 16:15 ` Dave Taht
2023-11-14 16:26 ` [NNagain] [EXTERNAL] " Livingood, Jason
2023-11-14 16:33 ` [NNagain] " Sebastian Moeller
2023-11-14 16:14 ` Sebastian Moeller
2023-11-14 16:37 ` Livingood, Jason
2023-11-14 17:00 ` Sebastian Moeller
2023-11-14 17:25 ` Vint Cerf
2023-11-14 17:43 ` Dave Taht
2023-11-14 18:10 ` rjmcmahon
2023-11-14 18:02 ` Jack Haverty
2023-11-14 18:10 ` Sebastian Moeller
2023-11-14 19:27 ` Jack Haverty
2023-11-14 19:40 ` rjmcmahon
2023-11-14 21:01 ` Dave Taht
2023-11-14 21:45 ` rjmcmahon
2023-11-16 3:41 ` [NNagain] Metrics for Network Managers (was FCC NOI due dec 1 on broadband speed standards) Jack Haverty
2023-11-16 6:57 ` rjmcmahon
2023-11-14 19:53 ` [NNagain] FCC NOI due dec 1 on broadband speed standards Sebastian Moeller
2023-11-14 20:01 ` David Lang
2023-11-14 20:37 ` Dick Roy
[not found] ` <CA+aeVP8dT-ynmHxNCmZq1OWdw3VBMMJTH0zsL6dGASvfKVpDMQ@mail.gmail.com>
[not found] ` <CA+aeVP9XyNd1rL_7S7U4OdvOwtVR8Sae8QvtiQLX0HMyzE57Xw@mail.gmail.com>
2023-11-14 20:55 ` [NNagain] Virtual mtgs and conferences vs. in-person ones (was) " David Bray, PhD
2023-11-15 0:58 ` Jack Haverty
2023-11-14 20:52 ` [NNagain] " Livingood, Jason
2023-11-16 0:27 ` Jack Haverty
2023-11-16 2:31 ` Robert McMahon
2023-11-14 18:16 ` rjmcmahon
2023-11-14 18:30 ` rjmcmahon
2023-11-14 17:58 ` Jeremy Austin
2023-11-14 18:08 ` Sebastian Moeller
2023-11-14 18:34 ` Livingood, Jason [this message]
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CCB5B6B9-8CB7-4952-ACFA-485147220762@comcast.com \
--to=jason_livingood@comcast.com \
--cc=jeremy@aterlo.com \
--cc=nnagain@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