Linked by Thom Holwerda on Thu 3rd Oct 2013 16:07 UTC

With the exception of Apple and Motorola, literally every single OEM we've worked with ships (or has shipped) at least one device that runs this silly CPU optimization. It's possible that older Motorola devices might've done the same thing, but none of the newer devices we have on hand exhibited the behavior. It's a systemic problem that seems to have surfaced over the last two years, and one that extends far beyond Samsung.

Pathetic, but this has been going on in the wider industry for as long as I can remember - graphics chip makers come to mind, for instance. Still, this is clearly scumbag behaviour designed to mislead consumers.

On the other hand, if you buy a phone based on silly artificial benchmark scores, you deserve to be cheated.

Thread beginning with comment 573810
To read all comments associated with this story, please click here.
not a cheat
by viton on Thu 3rd Oct 2013 18:34 UTC
Member since:

For accurate results benchmark needs stable frequency across the particular interval of measurement.

Reply Score: 3

RE: not a cheat
by Alfman on Thu 3rd Oct 2013 19:06 in reply to "not a cheat"
Alfman Member since:


"For accurate results benchmark needs stable frequency across the particular interval of measurement."

It's wrong to conduct the benchmark against a cpu/gpu super-configuration if the intention is to get an idea of the performance for a normal configuration (which it generally is).

Non deterministic behavior like this should be mitigated by conducting the benchmark over a longer period and/or repeating it a few times. At this point you get a better idea of min/max/avg/median/etc.

Changing the configuration for the benchmark makes the benchmark less accurate in terms of what it's trying to measure (even if the measurements are more consistent as you suggest).

O/T news: (every gov website for that matter) "Due to a lapse in funding, the US government has shut down.".

Reply Parent Score: 5

RE: not a cheat
by phoenix on Thu 3rd Oct 2013 19:14 in reply to "not a cheat"
phoenix Member since:


Are you trying to measure what the absolute best performance is for taskX or hardware-bitY?

Or, are you trying to measure the typical experience of a user doing taskX?

For the former, sure, enable the "performance" CPU governor, the "performance" GPU governor, switch to the "noop" disk scheduler, and run things at 100% utilisation. This is really only good for marketing purposes, since the battery life is atrocious if you actually run the phone/tablet like this.

For the latter, you want to measure how things work when they "race-to-sleep", how/if they bring extra cores online, etc. This is what people really want to see, but that no one wants to publish. The closest you get is in battery life tests.

Reply Parent Score: 4

RE[2]: not a cheat
by viton on Thu 3rd Oct 2013 19:53 in reply to "RE: not a cheat"
viton Member since:

Typical mobile workloads (non-games) occurs in bursts after some sleep. So likely it can run on max frequency. Throttled-down cpu in benchmarks will show worse performance than the device is actually capable of.

Reply Parent Score: 3