Totally disagree, single core perf means nothing to me, we have multithreaded everything these days.
I am not arguing with that, simply pointing out the potential of Apple Silicon for multi-core applications.
Even if the M1 had a single core performance increase over my i9 (I don't think it does), it only has 4 high performance cores, I have 10+. They just really don't compare in any way.
Well, M1 (an entry level SoC with peak CPU power consumption of 15W) multicore performance is
around 60-70% of that of a i9-10900K (enthusiast-level Intel with 10 cores and 20 threads and sustained power consumption of 125W). As far as single-core performance goes, the only currently commercially available CPUs that can outperform M1 are the end-of-the-line desktop Zen3 or the brand new Intel Rocket Lake.
As for the scale linearly -- that doesn't make any sense at all -- we don't know squat about scaling on an M1 because there's only 1 version right now, and it only has 4 performance cores and 4 low power cores.
Actually we do, since there are variants with 2 performance cores called A14. The M1 is around 70% faster in multi-code workloads than the A14 iPad, which is exactly the performance you'd expect from two extra performance cores while taking into account that both chips have identical 4 high-efficiency cores (1 Icestorm efficient core ~ 20% Firestorm performance core). Sustained power usage estimates of the iPad put it at around 7-10W, so M1 consumes somewhere between 50-100% power under load. I'd say that's quite good scaling.
The M1 cuts the clock on the 4 high performance cores in half when pushed to the limit heat wise, just like other processors. I've seen it every time I try to run more than one VM on it.
M1 base multicore clock is around 2.9ghz, peak turbo clock is around 3.2 ghz. That's very different from x86 CPUs where base clock is usually half of the peak turbo. As to why you are being severe throttling on your machine, I don't know. Possibly some bug or other unrelated issue. I've been doing very demanding stuff on my M1 laptop (large software builds, statistical simulation that take hours etc.) and I cannot replicate your experience.
How that? All benchmarks show that a Firestorm core running at 3.2 ghz/5 watts is very close in performance to a Tiger Lake or Zen3 running at 5ghz/20 watts. And again, look at the
Anandtech multicore benchmarks: M1 is outperforming Inte's latest and greatest Tiger Lake by 20% while consuming half the power. That's exactly why performance per watt is important: it simply allows you to build much faster chips.
The trick is we don't know how they'll connect them. Having all the RAM on a massively parallel Mx processor has it's own problems.
Well, sure, but then again, these are not new problems. They have existed for decades in HPC and GPU domain and they have been solved. When you look at M1 architecture closely, it is very clear that Apple is borrowing the experience of GPUs, with their massive memory bandwidth. Extremely high memory parallelism, quick context switches, multiple independent narrow memory channels to optimize parallel processing... M1 essentially uses a GPU-inspired memory controller connected to standard system RAM with optimized packaging. There is no reason to doubt that they will be able to further widen the memory bus to to 256, 512 or even 1024-bit — GPUs have been doing it for decades. In fact, I used to own an Apple laptop with a 1024-bit memory interface couple of years ago (Vega Pro 20). The current 5600M even has a 2048-bit memory bus!
Anyway, we'll just have to wait and see given the published information. Anyway, I'm just as interested to see what comes next as you are!
Agreed! And to make it clear — you are entitled to your skepticism and I absolutely respect that. It's just happens to be my hobby to discuss these things and to compare available information.