investigating Undesired 7950X3D core usage - MT uses the WRONG cores!

[Kreutzberg]

I am also still seeing threads going onto the non-cached CCD with the most recent patches.

[einarabelc5]

1.- What does your dcs.log say?

My 3900X goes like this

 

2023-05-29 23:25:05.533 INFO    EDCORE (Main): CPU: AMD Ryzen 9 3900X 12-Core Processor             [4x L3 caches]
2023-05-29 23:25:05.533 INFO    EDCORE (Main): CPU has uniform cache size 16777216 (per cache)
2023-05-29 23:25:05.533 INFO    EDCORE (Main): all CPU cores have the same efficiency class 0
2023-05-29 23:25:05.533 INFO    EDCORE (Main): CPU cores have different performance classes: [0-10]
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 10: {0, 1}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 10: {2, 3}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 9: {4, 5}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 8: {6, 7}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 7: {8, 9}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 6: {10, 11}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 5: {14, 15}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 4: {16, 17}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 3: {12, 13}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 2: {22, 23}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 1: {18, 19}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): logical cores with performance class 0: {20, 21}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): common cores: {8, 9, 10, 11, 14, 15, 16, 17, 12, 13}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): render cores: {0, 1, 2, 3, 4, 5, 6, 7}
2023-05-29 23:25:05.533 INFO    EDCORE (Main): IO cores: {22, 23, 18, 19, 20, 21}
2023-05-29 23:25:06.973 INFO    EDCORE (Main): Create boot pool.
2023-05-29 23:25:06.974 INFO    EDCORE (Main): Created boot pool: n:24
2023-05-29 23:25:06.975 INFO    APP (Main): Command line: "C:\Program Files\Eagle Dynamics\DCS World\bin-mt\DCS.exe" 
2023-05-29 23:25:06.975 INFO    APP (Main): DCS/2.8.4.39731 (x86_64; MT; Windows NT 10.0.19045)

2.-Did you set the MT executable to Performance in the Windows Display Settings? This forces the OS to recognize a 3D app.

I'm on a much older 3900X and see similar pattern, although the meaning is different as the CCD is much smaller on the Ryzen 2. I get the first core, then it skips along for about 5 or 6 cores and then allocates the last few.

 

The Settings screen is called Graphics Settings and you can reach it through the Display Settings right after the Multi-Display view configuration. In theory it shouldn't matter, but I've had issues with other programs like Tomb Raider where it helpsnull.null

Edited May 30, 2023 by einarabelc5

[Spectre1986]

nullHere are the results with the latest update. I've added foveated rendering through the OpenXR Toolkit, so the performance is better compared to my other screen shots. I do have DCS.exe added to the Windows 11 Graphics Settings and set to High Performance. It looks like the load is still spread across all cores, using both CCDs and the slow communication between them. The CPU is still the bottleneck with some pretty bad 18ms spikes. This is too high to maintain 90 FPS, which means it's not a good experience in VR.

It may be worth noting that the two CCDs also have different CORE performance. The first "gaming" CCD actually has lower maximum boost frequencies than the second "productivity" CCD. The extra cache is stacked on top of the cores, limiting their thermals, so the cores actually run a little slower on the gaming CCD.

This may have something to do with which cores are selected for certain loads. It may seem better to pick the faster cores on CCD 2 for some tasks and the cores with massive cache for others, but in reality this introduces latency because of the slow connection between the two CCDs. It would be better to pick one or the other for everything. History has proven that the massive cache is a huge advantage in flight simulators, but if you want to code it both ways I can test each. I'll run a complex mission and record FPS with whatever recording tool is recommended (I have experience with FRAPS) to show max, min, 1% lows, etc.

Here is the relevant portion of the attached log to match the previous poster's info.

2023-06-15 01:32:11.642 INFO    EDCORE (Main): CPU: AMD Ryzen 9 7950X3D 16-Core Processor           [2x L3 caches]
2023-06-15 01:32:11.642 INFO    EDCORE (Main): CPU caches have different sizes: [32-96] MB
2023-06-15 01:32:11.642 INFO    EDCORE (Main): Cores sharing L3 cache 96 MB: {8, 9, 10, 11, 6, 7, 4, 5, 12, 13, 2, 3, 0, 1, 14, 15}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): Cores sharing L3 cache 32 MB: {18, 19, 22, 23, 26, 27, 24, 25, 30, 31, 16, 17, 20, 21, 28, 29}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): all CPU cores have the same efficiency class 0
2023-06-15 01:32:11.642 INFO    EDCORE (Main): CPU cores have different performance classes: [0-14]
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 7: {8, 9}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 6: {10, 11}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 5: {6, 7}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 4: {4, 5}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 3: {12, 13}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 2: {2, 3}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 1: {0, 1}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 0: {14, 15}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 14: {18, 19}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 14: {22, 23}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 13: {26, 27}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 12: {24, 25}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 11: {30, 31}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 10: {16, 17}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 9: {20, 21}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): logical cores with performance class 8: {28, 29}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): common cores: {12, 13, 2, 3, 0, 1, 14, 15}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): render cores: {8, 9, 10, 11, 6, 7, 4, 5}
2023-06-15 01:32:11.642 INFO    EDCORE (Main): IO cores: {18, 19, 22, 23, 26, 27, 24, 25, 30, 31, 16, 17, 20, 21, 28, 29}
2023-06-15 01:32:13.106 INFO    EDCORE (Main): Create boot pool.
2023-06-15 01:32:13.107 INFO    EDCORE (Main): Created boot pool: n:32
2023-06-15 01:32:13.108 INFO    APP (Main): Command line: "D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR
2023-06-15 01:32:13.108 INFO    APP (Main): DCS/2.8.6.41066 (x86_64; MT; Windows NT 10.0.22621)
2023-06-15 01:32:13.108 INFO    APP (Main): Application revision: 221066
2023-06-15 01:32:13.108 INFO    APP (Main): Renderer revision: 24140
2023-06-15 01:32:13.108 INFO    APP (Main): Terrain revision: 24104
2023-06-15 01:32:13.108 INFO    APP (Main): Build number: 385
2023-06-15 01:32:13.108 INFO    APP (Main): CPU cores: 16, threads: 32, System RAM: 64654 MB, Pagefile: 4096 MB
2023-06-15 01:32:13.318 INFO    EDCORE (Main): (dDispatcher)enterToState_:0
2023-06-15 01:32:13.318 INFO    Dispatcher (Main): 2023/6/14 20:32 V1803061700
2023-06-15 01:32:13.341 INFO    ASYNCNET (Main): ProtocolVersion: 327
2023-06-15 01:32:13.345 INFO    ED_SOUND (Main): Using driver: wasapi

dcs.log

[Spectre1986]

Just for reference, this first screenshot is what the CPU load looks like in task manager with everything EXCEPT DCS running. So SimShaker for Aviators, Windows Mixed Reality, MS Paint, and Chrome.
null
The second screenshot is with all of this plus regular non-MT DCS. It stays on the first CCD as it should. You can see that the overall FPS reads lower, but the CPU frame time (Simulation) is much better and more consistent. They both "feel" about the same despite MT reporting a higher FPS. Probably because GPU shortfalls are handled better and are much harder to notice vs the hard studders caused by CPU latency.

Note: The attached screenshots and logs in this post are for the NON-MT version of DCS. Referred to as the standard version of DCS.null

dcs.log

[Kreutzberg]

This issue is still occurring with the latest DCS Open Beta version and latest AMD Chipset Drivers. Here is a picture from yesterday of my system on DCS in VR (7950X3D with BIOS set to prefer cache).

[mac22]

On 8/3/2023 at 11:34 PM, Kreutzberg said:

This issue is still occurring with the latest DCS Open Beta version and latest AMD Chipset Drivers. Here is a picture from yesterday of my system on DCS in VR (7950X3D with BIOS set to prefer cache).

1)also running a 7950x3d and I was about to mention the solution of setting the bios to cache (have never been able to get the other solution involving the game bar and optimizer to work!) - surprised this one is not working and it worked well for me on MSFS and some other games........

2)also when I tried to run the the MT.exe I get an almost immediate crash - is there any way to fix this? (note am running the SMT disabled)

[Archaic]

Is there an update on this?