I found out a very curious thing about DisplayLinkManager process. I'm running the latest drivers, version 5.6.1, Ubuntu 20.
Have your monitor connected and run `sar -u 1` to show the average CPU usage every second (you might have to install it using `apt install sar`). You'll see CPU usage of ~1%.
Keep the `sar -u 1` command running so that you see the changes that I'm going to show.
Now start the `System Monitor` and you can see the CPU usage jumping ~10%, while the system monitor window is open and visible. Going to the processes list, you will see the `DisplayLinkManager` is the process consuming the most CPU.
SO.... I guess we will be fine using the driver if we don't use System Monitor to confirm the CPU usage. Even if you use `htop`, the `DisplayLinkManager` process won't consume more that 1% of the CPU.
Let me know if your results are different from mine.
Cesário Canhão
I found out a very curious thing about DisplayLinkManager process. I'm running the latest drivers, version 5.6.1, Ubuntu 20.
Have your monitor connected and run `sar -u 1` to show the average CPU usage every second (you might have to install it using `apt install sar`). You'll see CPU usage of ~1%.
Keep the `sar -u 1` command running so that you see the changes that I'm going to show.
Now start the `System Monitor` and you can see the CPU usage jumping ~10%, while the system monitor window is open and visible. Going to the processes list, you will see the `DisplayLinkManager` is the process consuming the most CPU.
SO.... I guess we will be fine using the driver if we don't use System Monitor to confirm the CPU usage. Even if you use `htop`, the `DisplayLinkManager` process won't consume more that 1% of the CPU.
Let me know if your results are different from mine.