3 ms·
> ... In some tests, it is entirely probable that an i5 would smoke an M1 I'm aware that there is no such thing as a perfect benchmark. Geekbench has been usef
by xcv123 3y ago
> ... In some tests, it is entirely probable that an i5 would smoke an M1
I'm aware that there is no such thing as a perfect benchmark. Geekbench has been useful for me and is good enough to get a general idea of performance.
Check it yourself. Compare i5-4690k (fastest i5 from 2014) with my M1 Pro.
https://browser.geekbench.com/v6/cpu/compare/3356017?baseline=3265219 https://browser.geekbench.com/v6/cpu/compare/3356017?baselin...
M1 is faster in every single-core test in Geekbench 6. Overall 195% for single core and 427% for multi-core.
> an aggregate score of almost nothing meaningful or similar being compared
The dissimilarity between tests is intentional, by design, and is precisely what makes it useful as a general benchmark. The tests seem to cover a range of various real world use cases (C compilation, ray tracing, file compression, image processing, web browsing, etc). As I mentioned earlier, it usefully predicted real server performance at my job (JVM server doing financial batch processing).
- smoldesu 3y ago> The dissimilarity between tests is intentional, by design, and is precisely what makes it useful as a general benchmark. That's fine, if those numbers mean something to you then don't let me take that from you. My point is more that Geekbench has always been about cooking the books and avoiding objective comparisons. A number of their tests have been shown to instead rely on memory and SSD bandwidth, which kinda makes the whole "CPU score" concept bunk. Most benchmarks will indeed rank the 2021 RISC CPU above the 2014 CISC CPU. My point is more that Geekbench has always been a dubious point of comparison for hardware differences. The meaning behind those scores is pretty pointless when you actually see how they're weighed and aggregated.
- xcv123 3y ago> A number of their tests have been shown to instead rely on memory and SSD bandwidth These are simulating common CPU workloads, so of course they will be partly constrained by the processors memory controller bandwidth and latency, as in real workloads. The fact that this is the case makes it even more useful as a general processing benchmark. Modern processors include a memory controller in the package. What you see as "cooking the books" is actually the correct and expected approach for this purpose. It should rely on memory bandwidth for some of the tests. The entire Geekbench data set is ~1GB so would be cached by the OS in RAM on any of systems we care about benchmarking. If you need a specialized benchmark then run a specialized benchmark. Geekbench is not pretending to be something like a LINPACK benchmark.
- deleted 3y ago[deleted]