I have a MSI log file now for a ryzen 3.8 2667 in bf1 60hz. Its pretty difficult to analyze, and i cant identity the mins, and i dont think its correct. I read somewhere bf1 is supposed to issue 10 threads, but as i can tell there is at the same time activity in 14 threads. So the data seems wrong.
The utility of the threads besides the main thread always stays below 70% or more like in the 40-50%.
A typical picture on operations, amiens with high load on mainthread is is
9, 95, 53,14, 45, 6, 30,16, 47, 0, 19, 42,33, 2,13,2
(total 426)
5,100, 55, 9, 52, 2, 41, 41, 3, 47, 0, 44, 3, 25, 0, 23
(total 450)
Mind you i didnt have dips below 60fps and its cpu capped at 60fps. (same picture if cpu capped at 60fps or not), the main thread seems to stay a good deal lower for most of the time, this is corner cases.
My guess would be that as BF issues threads now, a ryzen will be single thread limited above aprox 100fps 1%min, so naturally on 144 7700k is a good deal faster here.
In general it is crazy how much cpu load bf1 have for a game in mode operation - amiens 64. And so many threads its using for a dx11 game from 2016. No wonder i5 have trouble lifting this kind of load on 4 cores even for 60fps.
Will have to try dx12 again and surely the scheduling is very important. Its just incredible to see how many threads bf1 can use, and also to that degree - if the data is correct.
I dont have the skill to analyze the situation in this game, but it seems we can have either complicated netcode or drawcall situations, pure cpu physics limitations, single thread and for the upper end of fps memory subsystem. They might play different roles depending on the 0.1% min fps demand or 5% min demand.
MSI file:
https://sabercathost.com/8V57/HardwareMonitoring.hml#.WMVNyHXmVEk
(select 2 (amiens) and 3 (scar plus amiens))