Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Indeed, 2522 is the official geekbench score. I’m not sure why any other would be chosen.
View attachment 2269705

If you look at the distribution, it’s multimodal. A lot of tests seem to be done under suboptimal conditions and produce less then ideal performance. For comparing the actual potential of the chip it makes sence to isolate the normal component with highest scores. For A17 Pro this appears to be 2925 with a standard deviation of around 10. For A16 it’s somewhere around 1630.
 
Tom's is useless because they copied last year's number for iPhone 14 Pro and pasted into this year's table. Web surfing tests can't be relied on because:

  • Web page contents change
  • Ads change
  • Browsers change
  • iOS changes
  • 5G cellular coverage changes
Interesting points. On the other hand, we have geekerwan admitting they rushed the review and that it probably had errors. I think we need to wait for more reliable testing.
 
  • Like
Reactions: souko
I trusted the aggregate score reported for the iPhone 14 pro at 2522.
But that's indeed less than the typical score. Do they use averages? If so, that's dumb. They should use medians as any sensible person would do...

Not sure. I ran GB6 on my A16 to get 2640.
 
Interesting points. On the other hand, we have geekerwan admitting they rushed the review and that it probably had errors. I think we need to wait for more reliable testing.

Everyone only had 3 days to do testing, but it's clear Tom's phoned it in.
 
Everyone only had 3 days to do testing, but it's clear Tom's phoned it in.
I mean, geekerwan admitted they phoned it in so...

Might be worth remembering that Tom’s got an official review unit. I’d be surprised if geekerwan did. So how did they get their unit and is it a pre-production unit, is it running the latest os etc. Very unreliable.
 
Indeed, 2522 is the official geekbench score. I’m not sure why any other would be chosen.

There is no "official" score. The number you shared is an average that changes daily. It includes submissions based on low power scores, low battery scores, throttled scores, cryo cooled scores.

The typical GB6 ST score for A16 running iOS 17 is about 2,600.

The typical GB6 ST score for A17 Pro running iOS 17 is about 2,850.
 
  • Like
Reactions: EntropyQ3
mean, geekerwan admitted they phoned it in so...

Might be worth remembering that Tom’s got an official review unit. I’d be surprised if geekerwan did. So how did they get their unit and is it a pre-production unit, is it running the latest os etc. Very unreliable.

What...?

Geekerwan is one of the most popular reviewers in the scene. They were literally at the launch event on September 14. It's very known Chinese reviewers have better media access to Apple due to the size of the Chinese market. That's why you see these one-on-one interviews with Tim Cook you never see with western reviewers.



1695161760439.png
 
There is no "official" score. The number you shared is an average that changes daily. It includes submissions based on low power scores, low battery scores, throttled scores, cryo cooled scores.
It’s as close to an official score as we have given it’s: from geekbench; and an average. It doesn’t change often after this many tests.
The typical GB6 ST score for A16 running iOS 17 is about 2,600.
The typical GB6 ST score for A17 Pro running iOS 17 is about 2,850.
It’s too early to say what a typical test is for the A17 chip. We know that many of the tests were conducted soon after the phone has been turned on, within the first couple of days. This means the chances that many background processes were still taking place is very high which could skew the average towards the lower end. We will need to see after many hundreds, or even thousands of tests have taken place to judge the “typical“ a17 scores.
 
What...?

Geekerwan is one of the most popular reviewers in the scene. They were literally at the launch event on September 14. It's very known Chinese reviewers have better media access to Apple due to the size of the Chinese market. That's why you see these one-on-one interviews with Tim Cook you never see with western reviewers.

View attachment 2269756

View attachment 2269755
OK, I did not know that. I must apologise I was in the wrong.
 
  • Like
Reactions: EntropyQ3
It’s too early to say what a typical test is for the A17 chip. We know that many of the tests were conducted soon after the phone has been turned on, within the first couple of days. This means the chances that many background processes were still taking place is very high which could skew the average towards the lower end. We will need to see after many hundreds, or even thousands of tests have taken place to judge the “typical“ a17 scores.

Do you think the reviewers were born yesterday? All of them who submitted GB scores? Or that Apple doesn't include such instructions and notes in the package they send to reviewers?
 
Do you think the reviewers were born yesterday?
I mean some of them aren’t particularly technical. All of them are rushed (Tom’s, geekerwan as they admitted) and benchmarking is full of nuance.
All of them who submitted GB scores? Or that Apple doesn't include such instructions and notes in the package they send to reviewers?
That doesn’t change the fact that given the rush you admitted the reviewers face, the benchmarks displayed lower scores early on than later. The effects of background set up processes on benchmarks are well known.
 

Bad news for all.

A17 Pro doesn't seem much better than A16 and yet, Qualcomm is now performing better for both CPU and GPU especially since A17 Pro consume way more power. I have to say since M1 released, so many developers left Apple and I think that might be the cause.

Don't expect too much from M3 series.
 

Bad news for all.

A17 Pro doesn't seem much better than A16 and yet, Qualcomm is now performing better for both CPU and GPU especially since A17 Pro consume way more power. I have to say since M1 released, so many developers left Apple and I think that might be the cause.

Don't expect too much from M3 series.
Better to wait for a review that doesn’t admit they rushed it and probably had errors. Especially when it seemingly contradicts other reviews.
 
You could fairly rapidly write/execute a benchmark that tests that "Decode" is 9-wide.
You could not perform decent tests to establish the OTHER claims that are made in that diagram in one day. I even put "Decode" in quotes because there may well be details as to exactly how wide decode is depending on many things (wider if executing out of loop buffer? wider if fusion?)

My guess is that Decode is wider (9 or 10) but Rename is not. A dumb microbenchmark that does not understand the issues would not pick that up.
The rest of your Jeremiad as to 3.5% IPC increase, disappointment, Apple skills, etc, well that's not technical so I won't touch it.
Did he (or she) say 'jeremiad'?

* edited for spelling and vocabulary expansion...
 
Last edited:
All reviewers make mistakes from time to time. So I wonder why Geekerwan's review is criticized so much. Is it because they're not Anandtench? Or because their review doesn't favor Apple? Or because they're Chinese?

Better to wait for a review that doesn’t admit they rushed it and probably had errors.
Who could be?
 
  • Like
Reactions: zakarhino and JPack
That is expected, but more importantly the Apple exec said they freeze the specifications of a given generation 3 years in advance, and not only that, they freeze the specifications for the camera system 3 years in advance as well, since I imagine both are tightly dependent on each other.
“B-b-but they lost one of hundreds of chip engineers a year ago, thing X that bugs me is clearly because of this” <- a common line of thinking her at MR.
 
All reviewers make mistakes from time to time. So I wonder why Geekerwan's review is criticized so much. Is it because they're not Anandtench? Or because their review doesn't favor Apple? Or because they're Chinese?

For me, there are too many conflicts with previously established baselines. The power consumption for A14/A15 reported by Geekerwan is dramatically different from what Anandtech reported for similar tests (by almost 80%)! E.g. Andrei measured over 4Watts for these chips running SPEC (and close to 5W in FP tests), Geekerwan only reports under 3 watts (7:18 in the video). These numbers do paint a daunting picture for Apple's 3N product, showing A17 pro being 20% less efficient than A16.

Now, at around 8:20 he reports a different set of numbers (I assume total device power draw?), which are much closer to Anandtech measurements. According to them, in SPECint A17 Pro is 10% less efficient than A16, 5% less efficient than A15, and about as efficient as A14. In SPECfp, A17 is as efficient or more efficient than there predecessors.

If we go from this second set of numbers (which IMO make more sense), it would appear that Apple is now targeting peak performance while trying to roughly maintain efficiency to previous generations. Maybe this is what the new CPU u-arch are about? More performance? Apple M-series have been criticised for their relatively low performance ceiling given the chassis capability, especially on desktop. Maybe the new core is designed to address those limitations. For the phone, slightly higher peak power consumption won't matter. For Mac, it could mean a nice performance boost.

P.S. Speaking of performance. Those SPEC2017 numbers quoted by Geekerwan are absolutely insane. That's comparable to an Intel i9-13900K, a 5.8Ghz enthusiast desktop GPU that draws over 30 watts for the same tests. I really don't understand how one can be disappointed by this level of performance at 5x lower power draw. People shoulder really adjust their expectations. Apple engineers seem to be held to such a high standard that it's considered a disappointment if their smartphone does not outperform an overclocked x86 workstation while consuming less power than an ARM mid-performance core. Come on.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.