HD (Ready): 1280 x 720 pixels
The Ryzen 9 5900X has a pretty big problem in this game, which could not be solved even by changing the platform to a B550 board. To understand what I mean, you need to take a closer look at the following FPS bar chart. With both dies (CCD) enabled, this CPU is significantly slower than the Ryzen 5 3600X. If you disable a complete CCD via the BIOS, the CPU becomes a pure 6-core and can suddenly play at the top again.
Why the performance with both CCDs turns out so bad despite high power consumption can hardly be explained by the motherboard. I have tested several BIOS versions (including a newer one than the one AMD distributed in the press folder), without success. Also the change to a MSI B550 Tomahawk did not bring any remedy. Here, one CCD was faster than two and even more economical. This will have to be observed, because I have also found a need for clarification in some workstation applications, which should lead to a similar cause.
Full–HD: 1920 x 1080 pixels
Frame times and percentiles of the Core i9-10900K are beyond any doubt, the CCD history of the Ryzen 9 5900X unfortunately continues here as well. Power is put in, but performance is poor. Reduced to only 1 CCD, the CPU is running again, which is quite strange.
WQHD: 2560 x 1440 pixels
The order doesn’t change and only the one-legged Ryzen 9 5900X can beat the Ryzen 5 5600X, which once again cuts a great figure and is much more efficient than its somewhat footsore big brother on two legs, which breaks away and is downright declassed.
Ultra-HD: 3840 x 2160 pixels
While all other CPUs are pushed together by the graphics card limit, the Ryzen 9 5900X with both active CCDs completely loses the connection, even though extremely much energy is consumed. You can’t understand this here anymore and it will be interesting to see how the Ryzen 9 5950X behaves, which is still to be delivered. With logic you won’t get anywhere at this point, because with a deactivated CCD the world is immediately back to normal.
The game is neither the most challenging nor the easiest in my collection, but it is the only one that generates such behavior, so it is unlikely to be fixed to the motherboard or the sample. Here you definitely have to retest, especially since AMD has unfortunately not responded yet.
Kommentieren