I have wondered for a few weeks why my CPU Usage is relatively high in idle.
Today I found out hat it does occur because of the liquidctl plugin for FanControl.
I do experience about 9-14% CPU usage from the Antimalware Service Executable (MsMpEng.exe) process when the plugin is enabled.
Compared to 0-0.5% CPU usage from the Antimalware Service Executable (MsMpEng.exe) process when the plugin is disabled.
In my case when the plugin is enabled:
the CPU also runs about 5°C hotter (due to not being able to throttle down when in idle),
the CPU clock is about 3 times higher,
the CPU power usage is on average 2 times higher.
From what I read, the other liquidctl plugin for FanControl (https://github.com/chenseanxy/FanControl.LiquidCtl) seems to addressed this issue by using Python.NET. Atleast that is what is mentioned in the README.md. I did not test the other plugin, though.
Due to having the goal to keep the computer quieter and cooler, I did disable the plugin for now, because it does not really benefit having it turned on in the current state because of this behaviour.
I do appreciate the work that was put into the plugin a lot.
I own a Kraken X61, which did not work out of the box, therefore I tinkered with it and liquidctl to get it working.
I have wondered for a few weeks why my CPU Usage is relatively high in idle. Today I found out hat it does occur because of the liquidctl plugin for FanControl.
I do experience about 9-14% CPU usage from the Antimalware Service Executable (MsMpEng.exe) process when the plugin is enabled.
Compared to 0-0.5% CPU usage from the Antimalware Service Executable (MsMpEng.exe) process when the plugin is disabled.
In my case when the plugin is enabled:
From what I read, the other liquidctl plugin for FanControl (https://github.com/chenseanxy/FanControl.LiquidCtl) seems to addressed this issue by using Python.NET. Atleast that is what is mentioned in the README.md. I did not test the other plugin, though.
Due to having the goal to keep the computer quieter and cooler, I did disable the plugin for now, because it does not really benefit having it turned on in the current state because of this behaviour.
I do appreciate the work that was put into the plugin a lot. I own a Kraken X61, which did not work out of the box, therefore I tinkered with it and liquidctl to get it working.
Is this issue something you recognized too?