> 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 part

> 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.