I’m not familiar with GeekBench, but I assume that, as with benchmarking software that I’ve used in the past, its benchmark runs for more than two seconds to help make numbers reproducible.
I haven’t checked what they do either, but I don’t see that as a reasonable assumption.
If they test for short burst performance specifically then the short runtime is the point. You then use multiple iterations of the test run to get a reasonable, reproducible result by averaging.
And can do that for two seconds before throttling.
I’m not familiar with GeekBench, but I assume that, as with benchmarking software that I’ve used in the past, its benchmark runs for more than two seconds to help make numbers reproducible.
I haven’t checked what they do either, but I don’t see that as a reasonable assumption.
If they test for short burst performance specifically then the short runtime is the point. You then use multiple iterations of the test run to get a reasonable, reproducible result by averaging.