←back to thread

1080 points antipaul | 3 comments | | HN request time: 0s | source
Show context
mcintyre1994 ◴[] No.25067338[source]
> The M1 chip, which belongs to a MacBook Air with 8GB RAM, features a single-core score of 1687 and a multi-core score of 7433. According to the benchmark, the M1 has a 3.2GHz base frequency.

> The Mac mini with M1 chip that was benchmarked earned a single-core score of 1682 and a multi-core score of 7067.

> Update: There's also a benchmark for the 13-inch MacBook Pro with M1 chip and 16GB RAM that has a single-core score of 1714 and a multi-core score of 6802. Like the MacBook Air , it has a 3.2GHz base frequency.

So single core we have: Air 1687, Mini 1682, Pro 1714

And multi core we have: Air 7433, Mini 7067, Pro 6802

I’m not sure what to make of these scores, but it seems wrong that the Mini and Pro significantly underperform the Air in multi core. I find it hard to imagine this benchmark is going to be representative of actual usage given the way the products are positioned, which makes it hard to know how seriously to take the comparisons to other products too.

> When compared to existing devices, the M1 chip in the MacBook Air outperforms all iOS devices. For comparison's sake, the iPhone 12 Pro earned a single-core score of 1584 and a multi-core score of 3898, while the highest ranked iOS device on Geekbench's charts, the A14 iPad Air, earned a single-core score of 1585 and a multi-core score of 4647.

This seems a bit odd too - the A14 iPad Air outperforms all iPad Pro devices?

replies(14): >>25067412 #>>25067414 #>>25067435 #>>25067467 #>>25067719 #>>25067879 #>>25067931 #>>25068427 #>>25068698 #>>25068977 #>>25069217 #>>25069354 #>>25070019 #>>25071266 #
simonh ◴[] No.25067435[source]
It may be possible the variations are due to differences in the thermal environment when the tests were conducted. I would expect the pro and mini to beat the air as they should have better thermals, but that may only show up over longer term tests and environmental factors could win out in shorter tests. Just a theory.
replies(1): >>25068009 #
joking ◴[] No.25068009[source]
if I recall correctly, the geekbench score does run on small bursts and it's designed to find the peak performance without taking the thermal limitations in account.
replies(2): >>25068191 #>>25069347 #
starfallg ◴[] No.25068191[source]
Hence why Cinebench is often used these days when evaluating real-world performance with sustained workloads.
replies(2): >>25069340 #>>25071195 #
reaperducer ◴[] No.25069340{3}[source]
Different tests. Different purposes.

GB deliberately avoids running up the heat because it is focused on testing the chip, not the machine's cooling ability.

Cinebench, as you say, tests "real-world" conditions, meaning the entire machine, not just the chip.

replies(2): >>25069798 #>>25072965 #
starfallg ◴[] No.25069798{4}[source]
The chip's ability to run at sustained load is a part of its design also. Precisely because modern chips has to throttle in order to meet power and thermal envelopes, we should be looking at sustained performance as a more accurate measure.

In a majority of cases, burst performance only affects things like responsiveness, and those things should be measured instead for a better reflection of the benefits.

replies(1): >>25070740 #
1. adolph ◴[] No.25070740{5}[source]
If you perform an integrated test, would you not perform unit tests? An unit test may show areas for easy improvement if other aspects of the total package are changed.

For example, if someone thought M1 was thermally constrained, they might decide to rip mini out of the case and attach a different cooling method.

replies(2): >>25072997 #>>25075394 #
2. gowld ◴[] No.25072997[source]
If you run only unit tests, you don't get useful data.

> they might decide to rip mini out of the case and attach a different cooling method.

99% of customers will never do this.

3. starfallg ◴[] No.25075394[source]
Not saying that burst performance shouldn't be measured, but it shouldn't be the de-facto go-to performance measure like it is now with geekbench.