• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Discussion Qualcomm Snapdragon Thread

Page 104 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
IMG-20240219-WA0063.jpg
I did this math, and I discovered that Firestorm in M1 has higher PPC than Firestorm in A14 Bionic, and even Avalanche in A15 Bionic.
 
Yeah I guess the Baidu guy made a mistake. With 3.2 GHz the M1 score/GHz goes from 2.47 to 2.31, placing it behind M2 as I would expect.

View attachment 101582

Unfortunately I think there are multiple errors for the frequencies. 7700x has a 5.4 GHz listed max boost, 13700k is also 5.4 GHz. Technically the 7700x has an Fmax of 5.55 GHz but it's unlikely to actually run that high in SPEC. For sure it's not getting 5.65 GHz. M2 clocks at 3.5 GHz (maybe 3.49 technically), not 3.45 GHz. I believe the X3 goes up to 3.36 GHz as well but someone could check me on that.

These results look a little suspect to me but I guess it's the best we have for now, but for sure, the listed frequencies are not reliable.
 
Unfortunately I think there are multiple errors for the frequencies. 7700x has a 5.4 GHz listed max boost, 13700k is also 5.4 GHz. Technically the 7700x has an Fmax of 5.55 GHz but it's unlikely to actually run that high in SPEC. For sure it's not getting 5.65 GHz. M2 clocks at 3.5 GHz (maybe 3.49 technically), not 3.45 GHz. I believe the X3 goes up to 3.36 GHz as well but someone could check me on that.

These results look a little suspect to me but I guess it's the best we have for now, but for sure, the listed frequencies are not reliable.
Yeah that seems dubious. Modern CPU frequency variations are a real pain for that kind of cross CPU uarch comparisons. I guess the only acceptable way would be to lock CPU frequency the closest possible to boost frequency, but I'm afraid that's not possible for all platforms.

I'm glad we don't have this issue when doing CPU simulations, we leave the pain to the implementation guys 😀
 
Stop testing exclusively desktop Intel/AMD chips on Spec for christ’s sake. Anyways, here’s another datapoint with MTL, Raptor Mobile, Phoenix, M3.
IMG_2275.jpeg
 
Back
Top