So where it matters is low-latency, realtime processes. If youāve ever watched your scheduler (not something most people would do, Iām a silly nerd) it bounces processes around core to core. Thereās various reasons why itāll shift a workload to another core, and outside of a kernel debugger you donāt know why but the point is it happens, and more often than youād think.
No big deal⦠except there IS a small penalty when that happens. It isnāt an immediate switch. Well with everything on a monolith die, it is near enough as makes no odds, hence why it can do that. However, the more separation there is, the less true that is. This is something that has to be accounted for in actual multi-processor systems. There the scheduler will NOT move things CPU to CPU unless thereās a good reason. Likewise, programs can tell the OS that they arenāt to span NUMA nodes unless absolutely necessary because of penalties in memory access speeds.
A chiplet design is not the same thing, thereās no NUMA, all memory goes through one controller, and the internal bus is much faster than the QPI/Infinity Fabric link. But it still takes more time than moving to a different core on the same chiplet, enough that it could potentially cause hitching in time critical tasks.
Gamers found this out back in the day, that disabling one of the chiplets lead to better performance since the game wasnāt using 16 cores, and it stopped the threads from getting bounced across the chiplets. Low latency audio could likewise be affected, since there is little time to tolerate stalls.
I donāt think it is likely an issue today, at least with patched Windows 11, it has an advanced scheduler that should be aware of the chiplets and schedule accordingly, though I havenāt been able to get confirmation of that, same as it is aware of the P-cores and E-cores and schedules accordingly. Just saying it was one thing I was aware of that was an issue back when they first went to that design.
As you say, either would work well, you canāt really go wrong. CPUs are getting stupidly powerful these days and youād need to be doing pretty huge templates before you started saying āman I could use more powerā with a current gen high-end CPU.