> Perf/watt isn’t the same thing as task energy, it sounds like you’re the one confused here. How do you calculate Perf/watt if not Task/Task Energy? > As I s

> Perf/watt isn’t the same thing as task energy, it sounds like you’re the one confused here. How do you calculate Perf/watt if not Task/Task Energy? > As I said, task energy (which is what’s measured in the OP) heavily favors “getting it done quicker” Which x86 can do. > It’s basically a “race to sleep” Oh no, it gets the task done faster! > I’m not the one claiming anything, if you disagree with Anandtech’s numbers go take it up with them. I have no issue with Anandtech, since they made no such claim. I read the article, you're badly misquoting it. > And again, that’s with it running at half the clock and half the threads of its laptop peers, so IPC is something like 8x higher in those scenarios. None of which is ultimately important. > That is not the kind of gap you close up with a node shrink or tightening pitches a bit. Hackernews experts know best though. Look at the results again. For example for SPEC2017 ST the Apple M1 MAX is essentially tied with the 5950x. Sure the M1 Max might be more energy efficent (though by how much you'd need to measure) - but remember it's a massively larger chip, a whole year newer, and on a newer node. For MT we see the M1 max bearely beat a 5800X for int, and do significantly better for floating point - which shows different priorities of design. Again, take a 5800X, shrink it down, add another FPU, and it beats a M1 max hands down. > Next year Zen4 and A16 will be on the same node, and then it’ll be another excuse for why x86 is still getting dumpstered. Except x86 isn't getting dumpstered. You're just cherry picking specific comparisons that make M1 look great, and then ignoring all contrary information. I mean, I could the the Borderlands 3 1080p benchmark, and say that the M1 got 21.1FPS to the GE76's 100, and therefore x86 is ~8 times faster. It wouldn't be honest (I'm deliberately chosing the worst M1 chip, and picking a workload that really favors x86) - but I could do it. But I don't, because it's not honest nor is it helpful.