AMD Comments on Threadripper 2 Performance and Windows Scheduler
Users may have been following Wendell from Level1Tech’s battle with researching the reasons behind why some benchmarks have regressed performance on quad-die Threadripper 2 compared to dual-die configurations. Through his research, he found that
this problem was limited to Windows, as cross-platform software on Linux did not have this issue, and that
the problem was not limited just to Threadripper 2, but quad-die EPYCs were also affected.
AMD Comments On The Findings
AMD stated that they have support and update tickets open with Microsoft’s Windows team on the issue. They believe they know what the issue is, and commends Wendell for being very close to what the actual issue is (they declined to go into detail). They are currently comparing notes with Bitsum, and actually helped Bitsum to develop the original tool for affinity masking, however the ‘NUMA Disassociator’ is obviously new.
The timeline for a fix will depend on a number of factors between AMD and Microsoft, however there will be announcements when the fix is ready and what exactly that fix will affect performance. Other improvements to help optimize performance will also be included. AMD is still very pleased with the Threadripper 2 performance, and is keen to stress that for the most popular performance related tests the company points to reviews that show that the performance in rendering is still well above the competition, and is working with software vendors to push that performance even further.
https://www.anandtech.com/show/13853/amd-comments-on-threadripper-2-performance-and-windows-scheduler
留意 :
Anandtech 分別在 Epyc 和 Threadripper 平台做測試 ( 使用CorePrio /不使用CorePrio )
結論 : CorePrio is a good temporary solution for sure, however it needs to be fixed in the Windows scheduler.