I was reviewing recent benchmark comparisons and noticed something odd with the baseline CPU scoring.
The baseline score being set at 2500 feels inconsistent when processors like the i7-12700 often land closer to 1900–2000 in Geekbench 5, even with high-speed DDR5 memory. That creates confusion when trying to compare actual performance scaling.
After checking Gideon’s browser extension, it seems the issue may not be raw CPU performance but rather how benchmark data is structured and interpreted. In some ways, this resembles an avi tag sequence problem, where the reported output depends heavily on how underlying data tags and sequences are organized rather than the visible final number itself.
Has anyone done a deeper breakdown of how these baseline values are assigned? Curious whether this is weighting methodology, reporting normalization, or something else entirely.
The baseline score being set at 2500 feels inconsistent when processors like the i7-12700 often land closer to 1900–2000 in Geekbench 5, even with high-speed DDR5 memory. That creates confusion when trying to compare actual performance scaling.
After checking Gideon’s browser extension, it seems the issue may not be raw CPU performance but rather how benchmark data is structured and interpreted. In some ways, this resembles an avi tag sequence problem, where the reported output depends heavily on how underlying data tags and sequences are organized rather than the visible final number itself.
Has anyone done a deeper breakdown of how these baseline values are assigned? Curious whether this is weighting methodology, reporting normalization, or something else entirely.