Quote from: _MT_ on March 25, 2021, 19:24:15
The point was that a single x86 core can outpace single Firestorm core if you take advantage of the second hardware thread. It's good to keep this in mind when comparing core counts.
I do not understand why people keep posting that same nonsense. Single thread means the performance that the core is able to deliver in that single thread. Most of the programs that you use are coded single thread ( the most basic and easiest to program ).
AMD and Intel can perform HT/SMT but that is tested in MultiThread benchmarks. As this requires programs that are multithread aware and programmed as such. And even then you can have bottlenecks where programs are single thread limited ( games where the main logic is in the main thread and thus limited your performance when that main thread is 100% loaded, while your other threads are doing a lot less ).
The fact that AMD/Intel can do better on a core per core basis with MT programs is not relevant for programs that use one thread ( what is something like 80% of the programs that you daily use ).
Nobody cares that AMD/Intel can do more workload in MT for a "core" basis because that is already included in ST vs MT benchmarks. I do not understand why one article resulted in such misinformation of the actual practical limitations of our software and how it works / interacts.
The fact that a M1 with barely a 2.5W a 3W / core is the same as a 13W core, is painful. Even if we add that HT/SMT to the mix, then a M1 core + 30% ( SMT/HT max gain is 30%, most cases less ). So lets make a 3W core, a 4W core. It is still using only 1/3 the power, for the same performance. Ok, lets say its not 7nm vs 5nm, lets add 50% watt gain from a process shrink in reverse ( make that 5nm a 7nm ). That becomes a 6W core vs 13W core.
This is the issue that people do not see. Excuses are excuses, ARM is simply more efficient and has been a for a long time on a watt / performance basis ( note: Apple unified memory etc also help ). Now we are just seeing it in practice on a desktop level field.