Higher than normal CPU usage on desktop/idle on Intel 12th Gen + RDNA3 platform

[RodroG-85]

Hello. I noticed again that the CapFrameX process shows higher than expected CPU utilization (constant CPU usage fluctuations, about 1% to 2%) on desktop/idle conditions with Overlay enabled using v1.7.1 and the latest pre-release beta build.

While in-game and capturing, the CX CPU % sensor shows continuous fluctuations from 0.0% to 0.3% max. This one seems a more expected percentage, though.

I had to roll back to version 1.6.8 to see a steady 0% CPU usage of CapFrameX.exe on desktop/idle/minimized-to-system-tray conditions with overlay features enabled. However, this version lacks many recent and new features, including Win 11 (coming from PresentMon v1.8.0 and later versions) and RDN3 support.

My system/platform specs are attached below: DxDiag.txt

Please, could you look into this?

Best regards.

[DevTechProfile]

I can confirm the behavior, see here: https://github.com/GPUOpen-LibrariesAndSDKs/ADLX/issues/11

[RodroG-85]

Thank you very much, as always, mate. Sorry for the delay. I was playing Starfield non-stop. 😄

Would it be possible to mitigate or fix this behavior?

El lun, 18 sept 2023 a las 19:28, DevTechProfile @.***>) escribió:

I can confirm the behavior, see here: GPUOpen-LibrariesAndSDKs/ADLX#11 https://github.com/GPUOpen-LibrariesAndSDKs/ADLX/issues/11

— Reply to this email directly, view it on GitHub https://github.com/CXWorld/CapFrameX/issues/255#issuecomment-1724052299, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANPEDJ4OOLFY7BCP3LDTE7TX3CAFBANCNFSM6AAAAAA42W2YNU . You are receiving this because you authored the thread.Message ID: @.***>

[DevTechProfile]

You can try to use the "ADL Fallback". At the end, it's up to AMD to fix this.

[RodroG-85]

Thank you. I will try it. Hopefully, AMD will take the report into account at some point.

[RodroG-85]

I've just seen that ADLX SDK was updated recently to v.1.1, but I don't know if this changes something regarding the issue.

https://github.com/GPUOpen-LibrariesAndSDKs/ADLX/releases/tag/v1.1

[DevTechProfile]

I've already updated the latest ADLX version.

[rphlrmblt]

Hello, just to add some salt : I've the same issue on two computers : Ryzen 9 5900X + 6700 XT and Ryzen 5 5600X + 6700 XT. Tried the ADL fallback but no improvement.

[DevTechProfile]

Got some tips from an AMD dev(?!). I've changed the ADLX API calls. Please check the following version (Build 110):

https://archive.capframex.com/

[RodroG-85]

Got some tips from an AMD dev(?!). I've changed the ADLX API calls. Please check the following version (Build 110):

https://archive.capframex.com/

Thank you! I will check it and will report back.

[rphlrmblt]

It seems better with the 110 version on the 5900X, I'll check also on the 5600X.

[RodroG-85]

@DevTechProfile CX CPU utilization on idle/desktop conditions is slightly better using build 110, but the issue persists. Using 110 ver, the app's CPU usage continuously fluctuates from 0.2 to 0.8% on idle/desktop, and on the same conditions with "ADL Fallback" enabled, the CX CPU usage now spikes from 0% to 0.1% all the time.

AMD should further mitigate CPU usage for their ADLX API calls.

[DevTechProfile]

Working on it. This has nothing to do with the AMD library.

Edit... it has something to do with the ADLX... ^^

[RodroG-85]

Working on it. This has nothing to do with the AMD library.

Edit... it has something to do with the ADLX... ^^

What a pity @DevTechProfile

So, can you do something to resolve or further mitigate the issue?

[DevTechProfile]

Looks like I've already fix it. Will upload a new version asap.

[DevTechProfile]

New problem, TBP is not being detected any longer. This AMD stuff kills me...

[rphlrmblt]

I'd some strange behaviour with some beta drivers from AMD (the FSR 3.0 related), I was missing some informations about the card like RPM Fan and so on. The 23.11.1 seems to be OK now. Can it be related to your problem ?

[RodroG-85]

New problem, TBP is not being detected any longer. This AMD stuff kills me...

@DevTechProfile how is it going?

[DevTechProfile]

@DevTechProfile how is it going?

I tried a lot of variants but at the end I came to the conclusion that the ADLX causes a significant CPU overhead, no matter what API calls I am using. It's up to AMD to fix that.

[RodroG-85]

I tried a lot of variants but at the end I came to the conclusion that the ADLX causes a significant CPU overhead, no matter what API calls I am using. It's up to AMD to fix that.

I hope the AMD guys do something and don't ignore the issue or take years to fix this CPU overhead. Given the current situation, you could add a warning informing the users about the issue.

[DevTechProfile]

I tried a lot of variants but at the end I came to the conclusion that the ADLX causes a significant CPU overhead, no matter what API calls I am using. It's up to AMD to fix that.

I hope the AMD guys do something and don't ignore the issue or take years to fix this CPU overhead. Given the current situation, you could add a warning informing the users about the issue.

AMD has fixed the issue as it seems. Try the latest Adrenalin driver together with latest beta on https://archive.capframex.com/.

[rphlrmblt]

My stupid "60+ seconds" idle on one of my PCs (an 5600X) :

• With AMD 23.12.1 but NO CapFrameX in background :

• With AMD 23.12.1 AND CapFrameX 1.7.2beta rev 111 :

There is a slight global increase of CPU consumption.

• With AMD 23.11.1 AND CapFrameX 1.7.2beta rev 110 :

There is a much hgher global increase of CPU consumption but better than ...

• In August :

Huge CPU usage, even in full idle !

So the improvements since the report are noticeable, especially on low end CPU (like 5600X), because on the 5900X with an 6700XT , even the 1.7.2beta rev111 improved things in he same test.

[RodroG-85]

AMD has fixed the issue as it seems. Try the latest Adrenalin driver together with latest beta on https://archive.capframex.com/.

Ok, I'm going to check this combo.

UPDATED: It's finally fixed! Thank you @DevTechProfile :-D

[DevTechProfile]

I am glad that the issue is fixed now.

[RodroG-85]

Sadly, the issue is back using the latest 1.7.2 release build together with 24.1.1 Adrenalin drivers.