From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] fcc request for standardized speed testing
Date: Thu, 19 Dec 2024 11:53:44 -0500 [thread overview]
Message-ID: <28f85903-cd0e-4cd0-909e-d94f5194a375@rogers.com> (raw)
In-Reply-To: <20241219084217.46016974@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
On 12/19/24 11:42, Stephen Hemminger via Bloat wrote:
> 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.
> _______________________________________________
Hmmn, and that's for non-mandated performance standards!
I'll speculate here that we have a "whack-a-mole" situation. No matter
how many holes you fix, you can't make a benchmark fair.
The interesting question is if you can make a "not less than" rule
system monotonically reduce the attack surface, instead of leaving it
the same size or worse (:-))
I know we do that with case law (I'm a former Quicklaw nerd) but it can
be /arbitrarily/ hard...
--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
[-- Attachment #2: Type: text/html, Size: 2768 bytes --]
next prev parent reply other threads:[~2024-12-19 16:53 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
2024-12-19 16:53 ` David Collier-Brown [this message]
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=28f85903-cd0e-4cd0-909e-d94f5194a375@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@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