From: Stephen Hemminger <stephen@networkplumber.org>
To: David Collier-Brown via Bloat <bloat@lists.bufferbloat.net>
Cc: David Collier-Brown <davec-b@rogers.com>
Subject: Re: [Bloat] fcc request for standardized speed testing
Date: Thu, 19 Dec 2024 08:42:17 -0800 [thread overview]
Message-ID: <20241219084217.46016974@hermes.local> (raw)
In-Reply-To: <0795300a-f3c4-4b7c-bd06-99d43de0a07b@rogers.com>
On Thu, 19 Dec 2024 11:31:08 -0500
David Collier-Brown via Bloat <bloat@lists.bufferbloat.net> wrote:
> On 12/18/24 17:17, David Lang via Bloat wrote:
> > so, what happens when a standardized test is mandated and then it's
> > found that that test isn't as good as others?
> >
> > I'm leery of any government mandates.
>
> Governments in general are good a "policing" things*, such as
> deficiencies in specifications and persons trying to weasel around them.
>
> At the same time, good specifiers write in "or better" clauses so that
> subsequent standards can be a few lines added to the original work.
>
> We can tell that is broken in Canada when the CRTC does a request for
> comments ... but then rejects all the comments and proposed amendments.
> Oh, and resists publishing them (:-))
>
> Have you seen that in the US?
>
> --dave
And it will just create benchmark cheating...
Look at any of the standardized database benchmarks as an example.
The benchmark starts out trying to an express a workload; then the vendors
discover new and creative ways to get higher numbers.
next prev parent reply other threads:[~2024-12-19 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 20:41 Dave Taht
2024-12-18 22:17 ` David Lang
2024-12-19 16:31 ` David Collier-Brown
2024-12-19 16:42 ` Stephen Hemminger [this message]
2024-12-19 16:53 ` David Collier-Brown
2024-12-19 22:59 ` Michael Richardson
2024-12-20 0:19 ` Kenneth Porter
2024-12-20 1:05 ` David Collier-Brown
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=20241219084217.46016974@hermes.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=davec-b@rogers.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