Ubuntu drivers eating a lot of CPU. Not always but at least 50% of the times
I have actually a very slow PC because of this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1541 root 20 0 2343424 51804 2624 S 111.9 1.4 198:49.14 DisplayLinkMana
in other words, DisplayLinkMana(ger) eats a lot of CPU. from 50 to more than 100%
sometimes not.
I think this is an issue, that should be fixed.
Thank you.
alfonso
-
Geoff commented
just got this dock and its just not going to work out if it stays this way. I only connected one extra monitor and two external hard drives. I have a new Inspiron 5570 i7 with 12 gigs of ram and a pci 512 m2 drive. I am running 18.04 fresh install of Kubuntu. I know its not the system or peripherals slowing things down... Its your product. Are you going to solve this problem or not. I will have to return it if there is no response to this.
-
Anonymous commented
Same issue here! Ubuntu 18.04 on xps13
-
Ben commented
Same issue here. Video is unbearably choppy. I am showing 4k@60hz on my external display, but displaylinkmanager service is consuming a minimum of 100% cpu while any drawing is going on. Even basic 1080p youtube video is too choppy to watch.
Anyone from Displaylink goona chime in here and hopefully find us a fix? Love the dock itself. Hate to have to return it. -
Ben commented
Same issue here. Video is unbearably choppy. I am showing 4k@60hz on my external display, but displaylinkmanager service is consuming a minimum of 100% cpu while any drawing is going on. Even basic 1080p youtube video is too choppy to watch.
Anyone from Displaylink goona chime in here and hopefully find us a fix? Love the dock itself. Hate to have to return it. -
Damian Chiliński commented
CPU utilization of DisplayLink on Linux strongly depends on particular application that is used. I noticed heavy CPU usage when compiz (compositor) is used comparing to when it's not. Also using remote Xorg display powered by DL device (export DISPLAY=10.0.0.2:0 on remote machine, when 10.0.0.2 machine is using DL) results in insane CPU load. There's a lot of cases that make DL display struggle significantly. However I think it's related to number of draw operations issues by certain software, comparing to others.
-
Anonymous commented
Same on HP Elitebook 1030 G2 x360 running Ubuntu 17.10, Targus ACP78US dock and Dell U3415W Monitor. The CPU utilization by DisplayLink Manager is consistently between 40% and 110%. Is this normal?
-
Anonymous commented
Tested with the latest Ubuntu 17.10, a Dell XPS13 9360, a Dell dock D3100 and 2 iiyama prolite screens, the driver works pretty fine but... after some niutes, it take too much CPU resources ! It's over 150%... CPU fans gonna be crazy and CPU temp reach 80° very quickly...
As a consequence, unfortunetly, I just cannot use the displaylink dock :(On my side, I can try to investigate more deeply if needed,
Thanks
-
Anonymous commented
I have the same issue. I'm using Dell Latitude 7280 connecting to Dell universal dock D6000, with two Dell monitors. The OS is Ubuntu 16.04.3 with kernel 4.10.0-35. The CPU goes very high and stays around 30% when idle. When resuming from sleep it keeps 100+% and don't go down even when idle.
-
Vytenis commented
It eats a lot of my CPU too on Fedora KDE. Normally 40-50%, but when I watch youtube, more than 100%.
-
Anonymous commented
Lots of people reporting very high cpu usage on Linux Ubuntu. I have got the same problem (but I can not report the bug, because I have no access to your support forum, neither I can not contact you directly, because the contact forms are not working...).
Example configuration:
OS info: Linux-3.16.0-77-generic-x86_64-with-Ubuntu-14.04-trusty
CPU info: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz Cache: 3072 KB Cores: 2
Installed RAM: 8097920 kB
DL driver version: 1.3.52
Hardware: ACER Aspire v3-371
Connected Devices on the docking station: USB-Mouse, USB-Keyboard, HDMI-Monitor (1920x1080), DVI-Monitor (1920x1080), RJ-45 Network Cable
CPU-Usage: 15-60%Removing the DVI monitor connection drops the cpu usage down to 0.7% (The system crashed after disconnecting the cable, but that's another bug, I guess).
Please fix this bug. Thanks.