Public bug reported:
Notice the time spent inside lxd-containers.service + lxd.service which
require network + disk subsystems to work before they can work.
This behavior can be recreated by installing + configuring LXD, with no
containers.
Both lxd-containers.service + lxd.service should be run asynchronously
or at end of boot process.
Boot should never hang waiting on these to finish.
Fixing this, will reduce boot time by 20secs or 10% of total boot time for this
machine.
_______
net11 # systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1min 16.744s
└─multi-user.target @1min 16.744s
└─lxd-containers.service @58.554s +18.188s
└─lxd.service @1min 14.295s +2.457s
└─network-online.target @1min 14.285s
└─network.target @1min 14.280s
└─ifup@eth2.service @55.020s
└─network-pre.target @54.598s
└─ebtables.service @50.416s +2.106s
└─local-fs.target @50.212s
└─var-lib-lxd-devlxd.mount @1min 16.572s
└─local-fs-pre.target @48.449s
└─lvm2-monitor.service @48.004s +220ms
└─lvm2-lvmetad.service @46.720s
└─system.slice @18.745s
└─-.slice @2.783s
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1700382
Title:
Boot times slow when LXD installed, due to poorly crafted systemd
dependency chain
Status in systemd package in Ubuntu:
New
Bug description:
Notice the time spent inside lxd-containers.service + lxd.service
which require network + disk subsystems to work before they can work.
This behavior can be recreated by installing + configuring LXD, with
no containers.
Both lxd-containers.service + lxd.service should be run asynchronously
or at end of boot process.
Boot should never hang waiting on these to finish.
Fixing this, will reduce boot time by 20secs or 10% of total boot time for
this machine.
_______
net11 # systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@"
character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1min 16.744s
└─multi-user.target @1min 16.744s
└─lxd-containers.service @58.554s +18.188s
└─lxd.service @1min 14.295s +2.457s
└─network-online.target @1min 14.285s
└─network.target @1min 14.280s
└─ifup@eth2.service @55.020s
└─network-pre.target @54.598s
└─ebtables.service @50.416s +2.106s
└─local-fs.target @50.212s
└─var-lib-lxd-devlxd.mount @1min 16.572s
└─local-fs-pre.target @48.449s
└─lvm2-monitor.service @48.004s +220ms
└─lvm2-lvmetad.service @46.720s
└─system.slice @18.745s
└─-.slice @2.783s
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700382/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
