DisplayLink Forum - View Single Post - High Cpu Usage (Lenovo Z50-70 Ubuntu 16.04)

kisten · 06-17-2016, 08:48 AM

Hi,

I've got the same setup as Fefbug. I'm using Gnome as desktop environment.

htop's showing me 37 DisplayLinkManager process instances.
When moving the mouse cursor in the build in laptop screen the cpu usage of the (probably) main process goes up to ~1%. But when moving the mouse cursor in the extern monitor it goes up to 50%-70% cpu usage and settles at around 20%.

I wouldn't have noticed it at all if it wasn't for the 'laggy' mouse cursor. Also it causes problems when moving the mouse cursor into different ui elements like the scrollbar or the menu, where the mouse pointer gets re-drawn. In such cases the mouse pointer briefly disappears and/or the 'old' pointer images will not be deleted, meaning you can see multiple mouse pointer images. Since the xps 13 got a Core i7 I'm actually more concerned about the 'poor' user experience caused by the mouse redraw problems. So I probably shouldn't have hijacked this Thread :-/. But it's a little bit connected to the cpu issue as well... I guess.

06-17-2016, 08:48 AM	#3
kisten Junior Member Join Date: Jun 2016 Posts: 2	Hi, I've got the same setup as Fefbug. I'm using Gnome as desktop environment. htop's showing me 37 DisplayLinkManager process instances. When moving the mouse cursor in the build in laptop screen the cpu usage of the (probably) main process goes up to ~1%. But when moving the mouse cursor in the extern monitor it goes up to 50%-70% cpu usage and settles at around 20%. I wouldn't have noticed it at all if it wasn't for the 'laggy' mouse cursor. Also it causes problems when moving the mouse cursor into different ui elements like the scrollbar or the menu, where the mouse pointer gets re-drawn. In such cases the mouse pointer briefly disappears and/or the 'old' pointer images will not be deleted, meaning you can see multiple mouse pointer images. Since the xps 13 got a Core i7 I'm actually more concerned about the 'poor' user experience caused by the mouse redraw problems. So I probably shouldn't have hijacked this Thread :-/. But it's a little bit connected to the cpu issue as well... I guess.