Performance Testing and Methodology
For general performance testing, we use a variety of applications and tests. Each test is run multiple times to ensure accuracy. The middle result is used in each case. The following system configurations were used for all benchmarking and testing.
Due to the scheduler improvements to Windows 10 build 1903, we decided to use build 1903 for all system testing. While many of the applications here have been used before in our motherboard reviews, even with the same configurations, the numbers are not comparable. Those were all done on builds 1803 and 1809 using the drivers that were current then. All systems were freshly formatted, and all the latest drivers and OS patches were used. All of the systems were updated to their latest BIOS revisions. Finally, for the Intel system, I did install the CPU microcode updates relevant to that CPU. It’s important to note that build 1903 does contain improved mitigations for several security flaws on Intel processors. However, I did not go out of my way to download any additional or optional mitigation patches. Hyperthreading also remained enabled for all testing.
Update: Windows version 1909 was used for the Core i9 10980XE. The 9900KF we tested was loaned to us, and updated testing under Windows 10 Build 1909 was not possible as the data was gathered before the 10980XE and the update to Windows 10 Build 1909. This also means that results are not included for Adobe Premiere CC or Ghost Recon Breakpoint.
We also followed AMD’s recommendations for using CPPC2 (where applicable) which is enabled by using AMD’s balanced power plan. Essentially, we created a “best case” scenario for each system outside of the hardware configurations. For the hardware, it was impossible to use the same memory modules on all of the test systems due to the nature of memory compatibility on different motherboards. That said, we were able to use common frequencies and keep the timings relatively close for the most part. This was not the case with the Threadripper system, which would not cooperate regarding running tighter timings. It simply could not complete all the tests at the same timings used by other systems. The timings in the table are the RAM’s default timings at maximum speeds. They were all run at 16,18,18,36,1T @ DDR4 3200MHz.
NOTE: For all Testing, the CPU was cooled with a Koolance Exos 2.5 system and a Koolance CPU-390 waterblock.
Finally, all systems were run at stock and overclocked values. The “stock” settings are their automatic or default base/boost clocks. The overclocked values are provided for the CPU being reviewed specifically.