Quote:
Originally Posted by Sparxy
Which compositor are you using, if any?
It can be noted that DisplayLink CPU usage tends to decrease when using a compositor that only redraws areas of the screen that have changed, as opposed to full-scene redraws.
High CPU usage while the entire DisplayLink screen is constantly updating (i.e. watching a video on it) is considered normal on linux.
|
I'm using Enlightenemnt (
www.enlightenment.org ) built from git. I've also tested with Gnome 3 and had the same results.
As for whether the entire screen was updating - there was an 'htop' terminal on ONE display, which was updated every second or so. Nothing else was happening. Regardless of whether there was screen activity or not, there is constant extreme CPU usage, and very large latency in updating the displays. This can't be "considered normal".