Just my opinion:
- Intel's Raptor Lake has too many E-cores
- The ratio of P-cores to E-cores was tilted in favor of P-cores in Alder Lake
- The ratio of P-cores to E-cores has tilted in favor of E-cores in Raptor Lake
- Because macOS treats all of these cores as identical cores, statistically speaking many more of the tasks we perform will be handled by E-cores
In an operating system that is blind to the difference between P-cores and E-cores, macOS becomes
E-core dominant with Raptor Lake.
With Raptor Lake, we’re mainly paying for E-cores. To be fair, P-core single-threaded performance has improved by a few percentage points, but the real improvement is in overall multi-core performance.
Single-threaded apps are statistically more likely to run on E-cores.
Multi-threaded apps will benefit from the overall increase in number of cores.
Apple went in the other direction when they created M1 Pro and M1 Max out of the original M1 design. In the Pro and Max variants, Apple decreased the E-core count by half and doubled the P-core count.
With Raptor Lake, Intel simply doubled the E-core count.
Depends on where in the stack you analyze. Raptor Lake's P cores have a better V/F ratio than Alder Lake. They clock higher, and also do so at a lower voltage than what Alder Lake would need to hit the same frequency. Alder Lake couldn't boost to 5.8 Ghz on 2 cores, with an all P-core clock of 5.5 GHz without high voltages and exotic cooling methods. Raptor Lake does this effortlessly out of the box (although 'stock' voltages are too high for what's needed for stability).
Also, another way to look at Raptor Lake is the value for the midrange. The 13700K has the same P+E core count as the 12900K, but comes in at a much lower price point. The 13700K also clocks higher than the 12900K does out of the box.
The 13600K has more E-cores than the 12600K, but the P-cores clock higher. The 13600K is only $29 more expensive than the 12600K, but you get 4 more E-cores, and higher clocks, and as you noted, much better MT performance. The 13600K outperforms the 12700K in many MT benchmarks. More performance, lower price.
Regarding the scheduling of threads on the E-cores vs P-cores, macOS is aware of the difference between P and E cores on ARM/Apple Silicon. We presume that the macOS x86 kernel isn't aware of nor interacts with Intel thread director, and that threads are equally likely to be scheduled on an E-core or P-core. But how are the Cores exposed to the OS in ACPI? Do the E-cores have a lower priority and thus likelihood to be scheduled to run a thread? Has anyone done an empirical analysis to know how good or bad thread scheduling actually is in macOS x86 in task-heavy programs on Alder Lake and now Raptor Lake? Could it be the case the threads are scheduled (more often than not) on P-cores rather than E-cores? I have never noticed a latency problem in macOS on Alder Lake, but others may have better information than me. One thing that I do notice is that in macOS Activity Monitor, Cores 0 & 1 are the most heavily utilized cores, and from what I can tell, those appear to be a P-core(s).
And while E-cores are much maligned (I think people will start to value E-cores as their IPC increases and they support instuctions such as AVX-512, probably when Darkmont comes), the E-cores allow intel to punch far above its weight in the $280 to $450 price point with the 13600K and 13700K. The 13600K pretty much destroys the 7600X/7700X in most non-gaming workloads at a lower price than the 7700x, and the 13700K trades blows with the more expensive 7900X in many tasks.
If and when Intel shrinks its manufacturing node to allow for more P-cores and E-Cores on the same package, AMD will struggle to keep up with its current line up. AMD will have to respond by offering more cores at a lower price to keep up. But can AMD do so (with only P cores and no hybrid E-cores) while keeping power consumption and temps in check? How can the $329 13600K embarass the $399 7700X in MT? E cores seem to allow Intel to offer more MT performance per die area.