Just as a point of reference, a single container booted on the same system I
showed the 38 second boot time before, seems to be down to 25 or so now.
Much better, but still not 10 seconds as it was.
Note that I don't call this a scientific test. I've made no real effort to
control the environment that I ran this in.
$ lxc launch ubuntu-daily:cosmic c2
Creating c2
Starting c2
$ lxc exec c2 /bin/bash
root@c2:~# systemd-analyze
Startup finished in 27.010s (userspace)
graphical.target reached after 25.342s in userspace
root@c2:~# systemd-analyze
Startup finished in 27.010s (userspace)
graphical.target reached after 25.342s in userspace
root@c2:~# dpkg-query --show snapd
snapd 2.35.4+18.10
root@c2:~# 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 @25.342s
└─multi-user.target @25.341s
└─snapd.seeded.service @5.268s +20.073s
└─snapd.service @13.190s +65ms
└─snap-lxd-9010.mount @18.054s +19ms
└─snap.mount @11.631s +9ms
└─local-fs-pre.target @437ms
└─keyboard-setup.service @212ms +223ms
└─systemd-journald.socket @204ms
└─-.mount @199ms
└─system.slice @199ms
└─-.slice @199ms
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796137
Title:
huge and slow image 20181002 due to seeded lxd snap
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1796137/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
