I don't why MacRumors keeps posting these articles.
Because it generates clicks, and because people are interested.
I don't why MacRumors keeps posting these articles.
I don't why MacRumors keeps posting these articles.
I think the difference in frequencies is sufficently consistent to reflect a real difference between the models.Ah. Not sure how things are going on macOS, but I know Geekbench had to move to guessing the clock on iOS long ago, because iOS won't reveal it any more.
Looks like on my M1 Pro Mac, sysctl hw.cpufrequency is no longer set (I think it was on x86 Macs), so maybe Geekbench has the same problem as on iOS that the API just doesn't exist. Instead, you can have powermetrics sample the CPU for a while and give you an average. I guess Apple feels that frequency varies too wildly for it to be meaningful. (There's also a bit of a Schrödinger thing going on. Measuring the frequency affects — ever so slightly — the frequency. Not to mention that the e-cores run on a different frequency than the p-cores…)
TL;DR: I wouldn't rely too much on that number either. And I hope Geekbench 6 allows for showing heterogenous cores.
But you can run Windows 11 for ARM, which is also capable to run (almost all) x86 apps through an emulator.You cannot run an Intel VM on an M1 or M2 device.
That's not what's important here. A single pair of PassMark results with a 2% difference could be due to run conditions or normal variation. The question under discussion is whether the GB reports of the CPU frequency difference between the M2 Pro and M2 Max are "real". You were skeptical of this, but the fact that PassMark also reports them supports that they are.A 6% clock increase but a 2% score increase?