From: Jonathan Morton <chromatix99@gmail.com>
To: dan <dandenson@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>, Rpm <rpm@lists.bufferbloat.net>,
libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] [Rpm] benton's consumer broadband label prototype
Date: Wed, 26 Oct 2022 19:10:01 +0300 [thread overview]
Message-ID: <A77C8CB5-1C0E-4DBD-B44C-1535A5E73916@gmail.com> (raw)
In-Reply-To: <CAA_JP8WeDT9sAgm2PByn_eePFk-mJxxK6m5eR9Y6WV7pb7nCGw@mail.gmail.com>
> On 26 Oct, 2022, at 6:09 pm, dan via Rpm <rpm@lists.bufferbloat.net> wrote:
>
> Also, my trust in the government to decide what's good or bad... laughable. You'd get things like on the example page. 903.5Mbps Median download speed, 811.8 Median upload speed, gaming rating poor and video conferencing marginal, on Fios service. I know that's an example, but it's so spot on what the government might do...
It's constructed as an example, and thus probably doesn't directly reflect any single service that actually exists.
The suitability rating for gaming and videoconferencing is undoubtedly derived from the packet loss rate, listed as 0.5% under "normal" conditions and over 5% under 10th-percentile conditions (which would occur pretty often, almost daily), and the high latency in the latter case (over 300ms). If I had a connection like that, I'd be pretty unhappy with its performance, no matter how much throughput it could get.
- Jonathan Morton
prev parent reply other threads:[~2022-10-26 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 2:30 [LibreQoS] " Dave Taht
2022-10-26 15:09 ` dan
2022-10-26 15:27 ` [LibreQoS] [Rpm] " Sebastian Moeller
2022-10-26 15:42 ` dan
2022-10-26 15:57 ` Dave Taht
2022-10-26 20:08 ` Sebastian Moeller
2022-10-26 21:50 ` dan
2022-10-26 16:10 ` Jonathan Morton [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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A77C8CB5-1C0E-4DBD-B44C-1535A5E73916@gmail.com \
--to=chromatix99@gmail.com \
--cc=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=rpm@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