- Joined
- Nov 3, 2011
- Messages
- 697 (0.15/day)
- Location
- Australia
System Name | Eula |
---|---|
Processor | AMD Ryzen 9 7900X PBO |
Motherboard | ASUS TUF Gaming X670E Plus Wifi |
Cooling | Corsair H150i Elite LCD XT White |
Memory | Trident Z5 Neo RGB DDR5-6000 64GB (4x16GB F5-6000J3038F16GX2-TZ5NR) EXPO II, OCCT Tested |
Video Card(s) | Gigabyte GeForce RTX 4080 GAMING OC |
Storage | Corsair MP600 XT NVMe 2TB, Samsung 980 Pro NVMe 2TB, Toshiba N300 10TB HDD, Seagate Ironwolf 4T HDD |
Display(s) | Acer Predator X32FP 32in 160Hz 4K FreeSync/GSync DP, LG 32UL950 32in 4K HDR FreeSync/G-Sync DP |
Case | Phanteks Eclipse P500A D-RGB White |
Audio Device(s) | Creative Sound Blaster Z |
Power Supply | Corsair HX1000 Platinum 1000W |
Mouse | SteelSeries Prime Pro Gaming Mouse |
Keyboard | SteelSeries Apex 5 |
Software | MS Windows 11 Pro |
The current Window 11 build is already aware of highest clocked CPU cores, hence only one good CDD is needed.It is quite the contrary to what you say. Scheduling will now be even more important to the point it becomes SUPER-DUPER-MEGA-EXTRA-important with cache on both CCDs. For this dual cache setup to work correctly, games/apps (via the scheduler) always need to request the cached data from the "correct" cache on the "correct" CCD or else you will suffer latencies from hell if/when data needs to be fetched from the cache across the CCDs because e.g. Core 3 requests data that was previously stored to the cache by Core 14 on the other CCD. Can't have a scenario like that. Ever.
So, both the scheduler and the CPU always need to "know" exactly "who" (which core) cached something (what) and where it was cached to avoid the dreaded inter-CCD and inter-cache latencies. This is definitely going to be a challenge and very complex on the level of correct scheduling and correct CCD assignment etc.
AMD does not exactly have the best track record when it comes to these scheduling and core assignment shenanigans so I would be quite surprised if they get this to work flawlessly out of the gate.
Personally, I have avoided multi CCD CPUs like the plague due to the Xbox GameBar and 'GameMode On' requirements (I have a PC and not a console, you muppets). It will be interesting to see if the GameBar requirement will be dropped now(?) since core parking will no longer be required.
We'll have to wait and see how well this is gonna work in practice. I would expect some growing pains, to say the least...
The problem with 7950X3D is non-X3D CCD has the higher clockspeed against lower clocked X3D CCD which is against standard Window 11's thread scheduler behaviour.
9900X3D/9950X3D should have one higher clocked CCD with X3D and lower clocked CCD with or without X3D.