These benchmarks do not represent real-world gameplay by any stretch of the imagination. These tests are conducted using built-in benchmarking tools utilizing the game engine. These tests are designed to stress the CPU’s power system as well as ensure proper functionality. These are all run at CPU limited resolutions to try our best to remove the video card as a bottleneck.
One additional note about gaming performance is that these are average values. They do not tell the whole story. Specifically, Destiny 2’s low’s and high’s help tell a very different story than what the average reports are.
For some reason, our results in this test were on the low side. I am uncertain why this was the case as the hardware in question is all identical to that of our earlier test systems aside from the board itself. The test was repeated multiple times with the same result.
Here we see results on the low side for a 3900X and our X570 Gaming X. However, it’s fairly close to the other test systems.
In this test, we see the polar opposite of the earlier gaming tests as the GIGABYTE X570 Gaming X dominates the other AMD test systems by nearly 10FPS.
We are back to a more middling result for the GIGABYTE X570 Gaming X. However, once again it’s extremely close to the other AMD test systems. In fact, they are within 1FPS of each other. However, Intel clearly has an advantage here.
Destiny 2 is a bit of a special case for AMD’s Ryzen 3000. Performance, when the initial workaround for these CPU’s and this game came out, was horrible. However, the gap is now almost closed between Intel and AMD. Although, for some reason, Destiny 2 loves HEDT systems as our 10980XE result shows.
Ghost Recon is now a lot more fun since they patched in a way to turn off the looter shooter elements of the game play. With that patch also came Vulkan support. Unfortunately, this test was still done with DirectX to keep the results comparable. We do see slightly better results out of the GIGABYTE X570 Gaming X than we do most of the other test systems, but this could admittedly be due to the patch. I’ll have to retest this at some point and gather new data, but I thought I would include it anyway.