In Process Lasso I can see that DCS.exe is using all 32 threads and upon inspection I can see that it is set to use only 0-15. I have a 7950X3D and I have observed the same behavior when running flat screen mode. Many performance metrics seem to be missing, for example I only get 0 for the "Simulation" frame time when pressing RCTRL+Pause twice and expanding the block of data, this frame time does seem to show on the graph though. ![]() This could explain the studders I experience in MT that are not present in standard. If this is true it seems the Xbox GB detects standard DCS as a game, but MT DCS as a productivity workload. nullįrom what I understand, AMD uses the "xbox game bar" to determine if the load is a game or productivity workload. Note: The overall FPS is higher with MT, but there is a noticeable studder. These seem to be most prevalent when burning units are moved into view, this causes the sharp green CPU spikes on the performance graph. There is a latency penalty when communicating between CCDs that can cause studders. ![]() The problem is that DCS MT uses SOME cores from both CCDs. The gaming CCD on my 7950X3D has 8 cores and 16 threads that share a massive 96Mb of cache, the other CCD only has 32MB and is reserved for productivity tasks (non-gaming).Īll games, including non-MT DCS, are automatically isolated to the gaming CCD as they should, which are the first 16 threads in Task Manager. AMD's new 7950X3D and 7900X3D have two CCD (clusters), with one dedicated to gaming.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |