Hello,
It's difficult to comment on 2 specific examples without seeing what you're trying to run them on.
The current Windows 10 and the Windows 7 DisplayLink drivers are 2 totally different architectures.
DisplayLink driver doesn't know what application you run, so it doesn't do any adaptation based on the web browser you are using. As you indicate that the issue is not present on IE, what led you to single out the DisplayLink solution as being the source of your CPU usage?
Also, you are seeing the CPU gauge, but the bottleneck may be the memory bandwidth and the CPU waiting on data copy...
Understanding your reasoning may help uncover other data you tested but didn't express here.
Regards,
Alban
|