3 ms·
Yeah, it’s the real world tasks that GeekBench tries to simulate that don’t tend to scale linearity with processor count. A lot of software does not take good a
by enneff 5y ago
Yeah, it’s the real world tasks that GeekBench tries to simulate that don’t tend to scale linearity with processor count. A lot of software does not take good advantage of multiple cores.
- fivea 5y ago> A lot of software does not take good advantage of multiple cores. It sounds pointless to come up with synthetic benchmarks which emulate software that is not able to handle hardware, and then use said synthetic benchmarks to evaluate the hardware performance.
- BobbyJo 5y agoIt has a very specific point: communicating performance to people who don't know hardware. Most consumers are software aware, not hardware aware. They care what they will use the hardware for, not what they can use it for. To that end, benchmarks that correlate with their experience are more useful than a tuned BLAS implementation.
- Teknoman117 5y agoThat's certainly true. But if that's your workload you shouldn't be buying a 64-core CPU... I use a few 32 and 64 core machines for build servers and file servers, and while the 64-core EPYCs are not twice as fast as the 32-core ones due to lower overall frequency, they're 70% or so faster in most of the things I throw at them.
- brigade 5y agoDoes Geekbench actually attempt to simulate that in their multi-core score? And how? I was under the impression that all of their multi-core tests were "run N independent copies of the single-threaded test", just like SPECrate does.