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
Bug solution in the commit d6d9763 maybe fixes a bug but it consumes CPU way too much in hidapi mode. The USB connection is re-established every time any data is sent to the wire.
When updating LEDs multiple times in a second in animation, the CPU usage gets high. I changed the code so that usleep is used again instead of re-establishing the connection and the CPU usage dropped to a minimal level even though I was updating LEDs 40 times in a second.
I was also looking towards a solution to reduce CPU load. My G815 displays CPU and RAM load and some other metrics, plus, some keys are animated. To fluidly display everything, I need an update rate that causes g815-led to consume 100 % load on one core and after a minute or so the data jams and is delayed due to too much data being processed. I set all key colors in non-commit mode and do one commit after each whole update to reduce latency/overhead but that does not seem to work at all.
Now most importantly: What did you change to make it work? Can you make a PR? Or show me your changes? I would be really interested in a solution.
Note that G-Hub manages this with < 1 % CPU load, so it is definitely technically possible.
Bug solution in the commit d6d9763 maybe fixes a bug but it consumes CPU way too much in hidapi mode. The USB connection is re-established every time any data is sent to the wire.
When updating LEDs multiple times in a second in animation, the CPU usage gets high. I changed the code so that
usleep
is used again instead of re-establishing the connection and the CPU usage dropped to a minimal level even though I was updating LEDs 40 times in a second.Related issues and PRs:
#45
#52
#63
#64
What would be the "Logitech" way to handle sending the data?
The text was updated successfully, but these errors were encountered: