Why would it be doomed to fail? Sure having more compute dies has a (usually quite small) scheduling penalty, but both AMD and Intel will have that since both Zen6 and NVL-S will have two compute dies on DT.
Also, scheduling is working fine in current CPU generations, despite having multiple compute dies too, so I don’t see why it should be doomed now all of a sudden in the next CPU generations.
Windows already can have scheduling problems with current gen, on both AMD and Intel, and this is a much easier sheme since its either all P-core on two different dies (Zen5) or a mix og P and E cores on a single die (Arrow Lake)
Nova Lake will take the issue to a other level with a mix of 3 different cores, intertwined on 3 different dies..
How do you suggest Windows should schedul a 12 thread gaming-workload with lots of crosstalk between the cores ?
Put all the work on a single compute-die and use 8P + 4 Ecores ? (Since Ecores have lower performance than Pcores you get lower performance)
Or split the work up between two compute-dies to only run on the Pcores ? (will get same crosstalk/latency issues AMD have been fighting for years and have pretty much solved at this point)
My main point is that Nova Lake will now pay the dual chiplet/compute-die tax which they avoided all the way up until now and "fanboys" have been criticizing AMD for.
While the Zen team almost have 10 years experience dealing with this now..
So i kinda fear we will see many problems with the 8P16E + 8P16E + 4LPE splitup since this is time they have to face scheduling workloads to different compute-dies on a highend desktop K-SKU, in recent times, and we already know how it went with Arrow Lake with its much easier chiplet architecture compared to Nova Lake (latency and gaming performance is very bad)