reported One or more cores reaching 100%

[scommander2]

8 hours ago, Special K said:

Can you disable the Nvidia overlay please and see if that changes anything? We had some users where the Nvidia overlay caused exactly that.

Hi @Special K, thanks for mentioning and it is a hint...  I would like to try out while NV overlay disabled.

Again, thanks a lots!! 

[Schlomo1933]

Am 6.6.2025 um 11:14 schrieb Special K:

Can you disable the Nvidia overlay please and see if that changes anything? We had some users where the Nvidia overlay caused exactly that.

I dont have the nvidia overlay, because i dont have nVidia Expierience installed. 

[Special K]

Am 4.6.2025 um 10:36 schrieb Schlomo1933:

@Dangerzone thank you for the advice , i have done it . Gigabyte Downloadservice and the Gigabyte Updateservice are not more shown in the tasklist.

But the GbtCloudMatrix is still shown in the DxDiag

@scommander2 i tried this. Here are  screenshots from taskmanager 

1- is Core 0-7 active

2-is Core 0-15 active

Can you please stop using process lasso or whatnot to activate / deactivate cores? DCS reads your CPU architecture and assigns specific tasks to specific cores. if you play around with that on your own, you work against what ED is doing for you already.

[Schlomo1933]

I have nothing running. as i told you i have a clean windows installation. i had just Parkcontrol one time activated to deaktivate coreparking. but its not running anymore just started once.

The only things i installed myself is the razr software for my keyboard and the oculus link app for my quest3 VR headset.

I made u some screenshots from the backround takes in taskmanager. maybe u will find some strange things. 

Btw: i installed also now Gforce Expierience to go shure that the nVidia Overlay is disabled.

.

Edited June 8 by Schlomo1933

[Special K]

vor 59 Minuten schrieb Schlomo1933:

I have nothing running. as i told you i have a clean windows installation. i had just Parkcontrol one time activated to deaktivate coreparking. but its not running anymore just started once.

The only things i installed myself is the razr software for my keyboard and the oculus link app for my quest3 VR headset.

I made u some screenshots from the backround takes in taskmanager. maybe u will find some strange things. 

Btw: i installed also now Gforce Expierience to go shure that the nVidia Overlay is disabled.

.

But how did you manage to get only your first cores used? You must have disabled the other cores (via lasso or TaskManager or Registry)

[Schlomo1933]

vor 3 Stunden schrieb Special K:

But how did you manage to get only your first cores used? You must have disabled the other cores (via lasso or TaskManager or Registry)

That’s the question. In all other games all cores work normal. How I said , it’s a fresh win 11 installation… 

Am 4.6.2025 um 10:36 schrieb Schlomo1933:

@Dangerzone thank you for the advice , i have done it . Gigabyte Downloadservice and the Gigabyte Updateservice are not more shown in the tasklist.

But the GbtCloudMatrix is still shown in the DxDiag

@scommander2 i tried this. Here are  screenshots from taskmanager 

1- is Core 0-7 active

2-is Core 0-15 active

Here is how it’s working via task manager as test .

1. Pic core 0-7 is active 

2. pic core is 0-15 active 

 

with all cores active: number 0 gets to 100% and cores 1-15 goes like to idle, while 16-32 goes also active 

 

[Schlomo1933]

What feels a bit strange for me is: 

The task manager shows me 32 cores 

but my processor has just 24 cores  and 32 threats.

[Special K]

vor 3 Stunden schrieb Schlomo1933:

What feels a bit strange for me is: 

The task manager shows me 32 cores 

but my processor has just 24 cores  and 32 threats.

Taskmanager always shows you logical cores.
Your CPU has 8 P-cores (each P-core has 2 logical cores) and 16 E-cores, which only have one core.
So you have 8 + 16 = 24 physical cores but 8x2 = 16 + 16 = 32 logical cores (aka threads, which is in all fairness wrong but nevermind)

So, when you see the first 8 cores loaded, that means that 4 of your P-cores are fully loaded and nothing else.
If you can replicate that somehow, I would really love to look at a DCS log for that case.

[Special K]

This is how it looks like (that's my CPU, but it looks similar).

 

[scommander2]

Hi @Special K, according to @Schlomo1933 CPU usage:

with his dcs.log:

common cores: {8, 9, 10, 11, 12, 13, 14, 15}
render cores: {0, 1, 2, 3, 4, 5, 6, 7}
IO cores: {16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31}
unavailable cores: {}

It seems that his system uses E-Cores in the most time rather than P-Cores (hope the CPU usage was taken when he was in the flight).

However, he set affinity by Task Manager fordcs.exe with all P-Cores 0-15 (with hyper-threading which matched to dcs.log common/render cores), then:

 

Edited June 8 by scommander2

[Special K]

vor 3 Minuten schrieb scommander2:

Hi @Special K, according to @Schlomo1933 CPU usage:

with his dcs.log:

common cores: {8, 9, 10, 11, 12, 13, 14, 15}
render cores: {0, 1, 2, 3, 4, 5, 6, 7}
IO cores: {16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31}
unavailable cores: {}

It seems that his system uses E-Cores in the most time rather than P-Cores (hope the CPU usage was taken when he was in the flight).

However, he set affinity by Task Manager fordcs.exe with all P-Cores 0-15 (with hyper-threading which matched to dcs.log common/render cores), then:

 

The first picture is ok, that is expected.

The P-cores are being used for the render pool (the ones with the higher scheduling class if available, ED named that performance class for whatever reason) and for the common pool. The E-cores are used for the IO-pool, if there are any. Otherwise, the IO-pool is empty and IO tasks will be handled by the common-pool also.

That is then shown in the 2nd picture, where the IO tasks will be spread also over the P-cores and the E-cores will not be used (that dcs.log would probably have shown an empty IO pool).

[Schlomo1933]

@scommander2 yes this was in flight.

@Special K what u mean with io-pool . Do you mean Input Devices ? 

[scommander2]

Thanks.  Then, I guess the 0-core with the 100% load must run the DCS main thread for graphic.

[Schlomo1933]

but why just one core for the graphic ?

 

And why so high ?

 

[Special K]

vor 5 Minuten schrieb Schlomo1933:

@scommander2 yes this was in flight.

@Special K what u mean with io-pool . Do you mean Input Devices ? 

DCS can use up to 3 threadpools:
- Render Pool => your rendering
- Common Pool => everything else but IO tasks (probably file and network operations)
- IO Pool => probably file and network operations

I am not an ED developer, so these are somewhat guesses.

vor 6 Minuten schrieb Schlomo1933:

but why just one core for the graphic ?

 

And why so high ?

 

Not sure if I asked that already, but do you run DCS as Administrator by chance? Or use the Nvidia overlay?

[Schlomo1933]

@Special K 

No , i dont run DCS as Admin .

And no , i dont use the nvidia overlay 

 

@Special K, @scommander2 thank you guys so much for your time and help. 

[Schlomo1933]

Is it possible that some registri changes from old windows installation was adapted by new windows installation?

[Schlomo1933]

@BIGNEWY can you please take a look to this thread? 

[scommander2]

I am wondering that core parking is enabled once to limit the load one on CPU?!

Edited July 3 by scommander2

[sleighzy]

7 hours ago, scommander2 said:

I am wondering that core parking is enabled once to limit the load one on CPU?!

It actually works in the inverse. The core is parked when there is less load, becomes idle, on it for power saving. As the load comes back on the core is unparked. This may be fine for normal workloads and power saving with things like laptops etc. for efficiency. However, when gaming when this happens rapidly, i.e. bursting loads, it is constantly parking and unparking the cores leading to latency issues. Disabling core parking means that the core does not "go to sleep" but is actively waiting for the next task.

[scommander2]

3 hours ago, sleighzy said:

It actually works in the inverse. The core is parked when there is less load, becomes idle, on it for power saving. As the load comes back on the core is unparked. This may be fine for normal workloads and power saving with things like laptops etc. for efficiency. However, when gaming when this happens rapidly, i.e. bursting loads, it is constantly parking and unparking the cores leading to latency issues. Disabling core parking means that the core does not "go to sleep" but is actively waiting for the next task.

Question: Is DCS required all CPU core unparked?

[sleighzy]

2 hours ago, scommander2 said:

Question: Is DCS required all CPU core unparked?

No reason not to (not sure if you can individually state which should be parked and which shouldn’t). DCS doesn’t “require” it per se. However, DCS doesn’t ask an individual core to do work. It requests the OS (CPU) to do work and the OS will schedule that task onto a core, which may be currently parked in which case it needs to “wake up”. 

[Special K]

Am 4.7.2025 um 14:58 schrieb sleighzy:

No reason not to (not sure if you can individually state which should be parked and which shouldn’t). DCS doesn’t “require” it per se. However, DCS doesn’t ask an individual core to do work. It requests the OS (CPU) to do work and the OS will schedule that task onto a core, which may be currently parked in which case it needs to “wake up”. 

That's not 100% correct. DCS creates core pools and schedules the tasks in these pools. With that, DCS decides what will be on which core groups at least.

[scommander2]

6 minutes ago, Special K said:

DCS creates core pools and schedules the tasks in these pools.

Thank @Special K.

If one parked core becomes the unparked state later while DCS has ran a while, it is too late for DCS to put this core into the core pool so DCS won't schedule a task on it. Is it correct?

Thanks.

[Special K]

Am 18.7.2025 um 08:32 schrieb scommander2:

Thank @Special K.

If one parked core becomes the unparked state later while DCS has ran a while, it is too late for DCS to put this core into the core pool so DCS won't schedule a task on it. Is it correct?

Thanks.

No it gets added to the pool on startup but might get parked before polled. So when it's needed it might not be in the state is should be causing the stutter until it's unparked again. See it as a database pool where the connections time out after a while but the pool doesn't know about their state. When you're unlucky enough to grab that connection from the pool, the database takes a bit longer to open that connection again as it would on an already open connection.