This is a very short-sighted approach. MCM is coming to Intel too. Moreover, hybrid architectures are coming to AMD with Zen 5. I've historically argued that Zen 4 X3D is a bit of a "beta test" prior to Zen 5, where scheduler improvements are going to be far more impactful when AMD moves to a hybrid architecture like Intel did with their 12th gen. Zen 4 X3D is the time to learn things and fix initial mistakes, before Zen 5 is much more of a prime time, especially in the data center.
This is going to require scheduler improvements not only from the microprocessor manufacturers, but the Windows, BSD and Linux kernels. There is going to be non-stop improvements to maximize the architectures.
Heck, Linux has an entirely new scheduler (https://www.phoronix.com/news/Nest-Linux-Scheduling-Warm-Cor...) being proposed that not only improves performance, but power efficiency, simply by keeping "hot cores hot", because the impact is far more relevant today than the last time the kernel's scheduler was seriously revisited. It's not like multi-core architecture is new either, it's just that the core count increase is going up so fast the impact keeps getting larger.
-- -----
Although I'd generally agree with a sentiment "don't bet on future things you don't have today" the reality is software is always catching up to hardware. Moreover, for major changes to CPU design, they don't YOLO out perfection in one pass -- it takes a while, by many large groups, over years, to eke every scrap of performance out of it.
NAND is a great example of this. The vast increase in IO has hamstrung a lot of stuff. Linux is straight up slamming into IO scheduler limits (NT kernel even more so) at a level that can be achieved by normal human beings, not big companies. That isn't because NAND is bad or flawed. It's because a near future where that kind of performance was possible wasn't considered in the IO scheduler's design.
In the case of Factorio, I'd bet good money that of ALL the game devs out there, the Factorio devs will be jumping all over this one to ensure it's resolved quickly.
This is going to require scheduler improvements not only from the microprocessor manufacturers, but the Windows, BSD and Linux kernels. There is going to be non-stop improvements to maximize the architectures.
Heck, Linux has an entirely new scheduler (https://www.phoronix.com/news/Nest-Linux-Scheduling-Warm-Cor...) being proposed that not only improves performance, but power efficiency, simply by keeping "hot cores hot", because the impact is far more relevant today than the last time the kernel's scheduler was seriously revisited. It's not like multi-core architecture is new either, it's just that the core count increase is going up so fast the impact keeps getting larger.
-- -----
Although I'd generally agree with a sentiment "don't bet on future things you don't have today" the reality is software is always catching up to hardware. Moreover, for major changes to CPU design, they don't YOLO out perfection in one pass -- it takes a while, by many large groups, over years, to eke every scrap of performance out of it.
NAND is a great example of this. The vast increase in IO has hamstrung a lot of stuff. Linux is straight up slamming into IO scheduler limits (NT kernel even more so) at a level that can be achieved by normal human beings, not big companies. That isn't because NAND is bad or flawed. It's because a near future where that kind of performance was possible wasn't considered in the IO scheduler's design.
In the case of Factorio, I'd bet good money that of ALL the game devs out there, the Factorio devs will be jumping all over this one to ensure it's resolved quickly.