You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, not sure if the root cause is an issue with the plugin itself or maybe with Stream Deck software updates but on current SD software version, comparing OHS plugin v1.2.2 against v1.3.0, the CPU usage has gone up quite a bit.
For reference, a profile on OG Stream Deck (where 14 out of 15 keys are OHS) CPU usage of StreamDeck.exe or Qt QtWebEngineProcess.exe (depending on whether or not the Elgato software is in focus) has increased from around 5% to 9-15%.
This is entirely possible to have been caused by Elgato themselves as I don't recall the usage being even at 5% couple of months ago, but just something I wanted to bring attention to (Higher CPU usage persists even when switched away to other profiles).
CPU usage drops to pretty much zero once the plugin is uninstalled.
The text was updated successfully, but these errors were encountered:
The only change was in the drawing of the image which is pretty lightweight. However, the webbrowser based StreamDeck software has been getting more bloated.
Hi, not sure if the root cause is an issue with the plugin itself or maybe with Stream Deck software updates but on current SD software version, comparing OHS plugin v1.2.2 against v1.3.0, the CPU usage has gone up quite a bit.
For reference, a profile on OG Stream Deck (where 14 out of 15 keys are OHS) CPU usage of
StreamDeck.exe
orQt QtWebEngineProcess.exe
(depending on whether or not the Elgato software is in focus) has increased from around 5% to 9-15%.This is entirely possible to have been caused by Elgato themselves as I don't recall the usage being even at 5% couple of months ago, but just something I wanted to bring attention to (Higher CPU usage persists even when switched away to other profiles).
CPU usage drops to pretty much zero once the plugin is uninstalled.
The text was updated successfully, but these errors were encountered: