gpu-manager's drm output detection affects boot time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-drivers-common (Ubuntu) |
Fix Released
|
High
|
Alberto Milone | ||
Xenial |
Fix Released
|
High
|
Alberto Milone |
Bug Description
SRU request:
[Impact]
The current drm code to probe the connected outputs is too resource intensive, and slow down the boot process.
[Test Case]
1) Boot Ubuntu and run the following command, looking for gpu-manager:
systemd-analize blame
This will show how long gpu-manager took. Write down the number
2) Install the package from -proposed, and run systemd-analize blame. See if the number has become smaller.
[Regression Potential]
Low, all the changes are already included in Yakkety.
_______
Rather than calling drm directly, gpu-manager should simply check the outputs connector status by using the sysfs filesystem (e.g. /sys/class/
This should make gpu-manager a bit less resource intensive, especially on boot.
The attached perf shows the problem in gpu-manager.
Changed in ubuntu-drivers-common (Ubuntu): | |
status: | Triaged → In Progress |
Changed in ubuntu-drivers-common (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Alberto Milone (albertomilone) |
description: | updated |
Changed in ubuntu-drivers-common (Ubuntu): | |
status: | In Progress → Fix Committed |
I committed a fix in Yakkey but aptdaemon is currently broken (LP: #1496292), so ubuntu- driver- common won't build.