(no title)
feelix | 5 years ago
The source of the confusion has been the benchmarking software. To saturate one core on an Intel processor you need to run two threads, because that's the way they are designed. So the single thread benchmarks that have been used so far have been using 50% of the capacity of an Intel CPU core and comparing it with 100% of the capacity of an M1 CPU core.
This article breaks it down fully: https://wccftech.com/why-apple-m1-single-core-comparisons-ar...
gjsman-1000|5 years ago
More discussion: https://linustechtips.com/topic/1276532-exclusive-why-apple-...
feelix|5 years ago
I guess at the very least CPU benchmarking software should have a "thread to thread" benchmarker alongside a "core to core" benchmarker, or something along those lines.
That would be in the spirit of having benchmarks indicate real world usage
rsynnott|5 years ago
The main purpose of single-threaded benchmarks is to approximate performance for things which are actually single-threaded.
Jonnax|5 years ago
SMT is designed to boost performance in multitreaded workloads.
It can be thought as multitasking for a CPU core.
Using two threads for one benchmark and use one thread for another, it is not comparing single core performance.
Because why wouldn't that CPU schedule the load on other cores?
cpgxiii|5 years ago
The argument to be made is that because of the resources dedicated to SMT, single thread on AMD/Intel versus single thread on Apple is not measuring the true potential performance of the whole core. In principle, some multithreaded workload over all available threads could be a better metric for whole-processor performance.