Yeah, that's just plain silly. Either stop pretending it's reflecting a CPUs (instead the test case's) multi-core performance, or change it to something embarrassingly parallel.
You almost made it sound as if multi-core performance is only measured by embarrassingly parallel tasks. If it's what people want, then they should use some rendering or parallel compilation benchmark.
Or focus on the subscores of GB that show how these tasks scale:
Benchmark results for an ASUS System Product Name with an AMD Ryzen 9 7950X3D processor.
browser.geekbench.com
- clang: x14
- ray tracer: x19
Looks like good scaling for a 16-core CPU.
Thing is we don't have enough information about bottlenecks (are these due to a benchmark issue [implementation or just inherently not scalable] or a CPU issue?).
All I could find was this:
https://www.geekbench.com/doc/geekbench6-cpu-workloads.pdf and it doesn't tell anything about the MP aspects.
That's not GB specific, all closed source benchmarks suffer from that.
And another issue is that scaling changed dramatically between GB 5 and GB 6. And I personally think it's a good thing as GB 5 scaling didn't mean anything to me.
Benchmark results for an ASUS System Product Name with an AMD Ryzen 9 7950X3D processor.
browser.geekbench.com
But I'm sure many people now are happy GB 6.1 improved their chip's multi-core performance...
The problem is some think a single aggregated number can represent a CPU performance. And definitely GB 6 MP number doesn't. Like any other benchmark.