They don’t have a consistent methodology for measuring power consumption, which makes the efficiency comparisons hard to reason about. I think the “real” efficiency of the Oryon platform is higher.
To be fair I think it is the same as their usual methodology, just with CB R24 instead CB R15/23, no? And they did rerun CB R24 on the other processors listed with this method, which is unfortunately just a subset of the ones they have performance scores for, so it should be comparable for the ones they have in their graph. That said, it is a single benchmark from a small set of devices with no repeats. Always a concern that a review site gets a lemon or a statistical outlier in either direction by random chance.
However, I am very surprised about the performance. The 4.2GHz SKU can barely match the 3.7GHz M2 in Cinebench - what is happening here? These are supposed to be designs with quite similar architecture, is Oryon running lower frequency than advertised or is there some other problem?
For the CB R24 single core right? I think they tested the 4.0 GHz Snapdragon (it's the 80, they're still waiting on the 84) though I think the M2 Pro is actually 3.5GHz. As far as I can tell the 3.7GHz was only on full M2 Max and M2 Ultra SOCs (basically Apple doing a small bump like say for a desktop SOC
). M2 Pros and binned M2 Maxes seem to be 3.5 GHz. And I think that's why the SC efficiency score is so bad relative to the M2 Pro.
This is what Qualcomm told people to expect though, so it's not like the tested SOC is a lemon or some statistical outlier in terms of performance. That said, yeah it could be a problem with the an unoptimized benchmark for the SOC ... we see GB6.2 SC score much more reasonably here. My guess is GB 6 is much closer to the truth for most workloads which also makes the efficiency estimate based on that score unreliable and admittedly also makes the CB R24 MT benchmark a little suspect too.
Also, the multi-core performance is alarming IMO. With 3x as many performance cores Oryon only manages 60% better performance than M3 and is practically equivalent to the 8+4 M2 Pro. I thought it was supposed to be a server core with very good performance at lower power consumption? Is there an issue with Cinebench running on the platform?
Unlike with SC, it's not like GB6.2 tells a different story here. True it has its own (justifiable) quirks with MT scaling, but ... the scores are what they are. To really nail it down, we would need to get another test, maybe GB5 to confirm what is going on (or GB6 multicore sub-scores known to scale linearly with core count). If it is true, this where I get into my 3 reasons above for why Qualcomm's multicore scores are underwhelming. I suppose I should include unoptimized CB R24 benchmark as a fourth - but it was CB R23 that was really bad, though? at least on Macs CB R24 behaves reasonably and the part that we suspected was the culprit for CB R23, NEON, is shared between the Mac and the Qualcomm CPUs.
Hard to say. Not a good source usually but Maxtech tested one of the models with Hwinfo reporting the frequencies during some tests. It does seem the X Elite lowers frequency quite soon and continues at that speed or drops further.
That was on battery though and for the multithreaded test too I think. Basically it undercuts his "the performance doesn't change on battery" line he kept repeating over and over again - single threaded performance
might not, multithreaded performance clearly was affected being on battery. His battery MT score is much lower than NBC's for the same Surface device. Also the video had other problems. In fairness to the Snapdragon, unlike what Vadim claimed in the video, the Adreno GPU has ray tracing and Ryan Shout in his, admittedly paid,
preview had Solar Bay working and we know Solar Bay works on Android devices with Adreno. That said, both these reviews and others have mentioned frequent crashes and instability issues with benchmarks, but most of those as far as I could tell were with emulated programs. Unless Solar Bar is non-Windows ARM native unlike the rest of 3D Mark's supposedly is, it should've worked.
Basically another brammer of a video from MaxTech.