Re:Intel microcode license updated to permit redistribution
by mannykannot on Friday August 24, 2018 @06:46AM
(#17834095)
Intel's attempt to suppress independent benchmarking suggests that this is not the whole story. This suspicion lingers even though it has removed the clause.
[ Parent
| on HN ]
Re:Intel microcode license updated to permit redistribution
by yvdriess on Friday August 24, 2018 @10:42AM
(#17835194)
There exists other reasons to not allow third-party benchmarking, other than trying to hide something. A common reason is as a way to make sure the benchmark is done in a proper way.
I've had the experience myself, and I can imagine that when a system is complex and hard to measure that you don't want an internet journalist running Cinebench to become the reference benchmark for your customers.
Re:Intel microcode license updated to permit redistribution
by Skunkleton on Friday August 24, 2018 @01:34PM
(#17836393)
Yeah, but what if the microcode killed cinebench performance? Wouldn't that be interesting?
Re:Intel microcode license updated to permit redistribution
by Joky on Friday August 24, 2018 @03:21PM
(#17837226)
The problem is still the context in which cinebench would be ran. There are so many variable on a complex system that "the microcode killed cinebench perf" could very well be an over simplification of "the microcode in conjunction with this particular motherboard and this version of the kernel plus this particular Nvidia driver lead to a bad interaction that affects cinebench performance negatively".
Re:Intel microcode license updated to permit redistribution
by mannykannot on Friday August 24, 2018 @11:56AM
(#17835725)
That's a fair point, though the best solution would be for Intel to commission independent or independently-audited benchmark tests.