Fix high CPU usage on ENE DRAM modules. #59
+33
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, I tested your branch. However, even after compiling successfully, I’m still seeing high CPU usage (around 21%) whenever I use effects on the GPU or on the memory modules. Thanks for your work on this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't own the same specs as the issue reporter (GitLab issue #5124). Could anyone check if these changes mitigate the issue.
This PR addresses the excessive CPU usage observed when controlling ENE-based DRAM RGB modules on Windows. Users reported CPU spikes up to 10% when enabling multiple RAM modules, caused by repeated calls to pawnio_execute during SMBus transfers.