You are not logged in.
I've been running systemd for a month now and been optimizing boot all along. I've come down from 28s to 13s but with the systemd-tools/udev package it went up again to 17s. Can't really tell why.
Before systemd-tools update;
Startup finished in 7414ms (kernel) + 5575ms (userspace) = 12990ms
1817ms systemd-tmpfiles-setup.service
700ms console-kit-daemon.service
427ms systemd-logind.service
411ms console-kit-log-system-start.service
388ms sshdgenkeys.service
380ms crond.service
376ms rpcbind.service
349ms systemd-remount-api-vfs.service
212ms systemd-vconsole-setup.service
184ms home.mount
150ms dev-hugepages.mount
125ms udev-trigger.service
120ms systemd-modules-load.service
115ms systemd-sysctl.service
115ms sys-kernel-debug.mount
114ms dev-sda3.swap
114ms dev-mqueue.mount
112ms rpc-statd.service
107ms sys-kernel-security.mount
92ms media.mount
92ms remount-rootfs.service
84ms udev.service
48ms eth0-network.service
20ms dbus.service
11ms systemd-user-sessions.service
5ms mnt-SERVER_NYTT.mount
0ms sys-fs-fuse-connections.mountWith systemd-tools/udev;
Updated systemd 20120601 ----------------
Startup finished in 7356ms (kernel) + 9600ms (userspace) = 16957ms
2010ms mnt-SERVER_NYTT.mount
1297ms systemd-vconsole-setup.service
995ms systemd-remount-fs.service
624ms systemd-tmpfiles-setup.service
409ms dev-sda3.swap
350ms console-kit-daemon.service
318ms systemd-udev-trigger.service
300ms dev-hugepages.mount
164ms systemd-modules-load.service
159ms sys-kernel-debug.mount
159ms systemd-sysctl.service
154ms dev-mqueue.mount
145ms systemd-udev.service
141ms home.mount
125ms console-kit-log-system-start.service
121ms systemd-logind.service
106ms eth0-network.service
93ms crond.service
79ms rpcbind.service
71ms rpc-statd.service
33ms dbus.service
19ms systemd-user-sessions.service
1ms sys-fs-fuse-connections.mount
0ms tmp.mountAs you can see no service is directly to blame.
Ooops! Just saw in journal that TWO udevs are started!;
Jun 03 09:38:18 mediadatorn udevd[37]: starting version 182
Jun 03 09:38:18 mediadatorn udevd[122]: starting version 184Only one udevd listed in processes though. So it seems that two different instances of udev are tried to start from somewhere. What's up with this?
Last edited by swanson (2012-06-03 08:05:01)
Offline
Did you try rebuilding your initrd image and rebooting?
Offline
Will do. There are new kernels now ...
Offline
Always something new;
Bootup is not yet finished. Please try again later.
664ms console-kit-daemon.service
...After a while;
Startup finished in 6936ms (kernel) + 67973ms (userspace) = 74910ms
60124ms mnt-SERVER_NYTT.mount
664ms console-kit-daemon.service
...I'll look into this, it's my nfs client mount which acts up. But the tip to rebuild initramfs seems to great! Thanks.
Now into systemd and nfs again...
Offline
After several tests I went back to the fstab/systemd mount method (comment=systemd.automount) for the nfs share. And I got;
Startup finished in 6986ms (kernel) + 8050ms (userspace) = 15036ms
811ms systemd-udev-trigger.service
786ms systemd-vconsole-setup.service
784ms dev-hugepages.mount
782ms systemd-remount-fs.service
634ms systemd-modules-load.service
633ms systemd-sysctl.service
630ms sys-kernel-debug.mount
629ms dev-mqueue.mount
579ms systemd-udev.service
514ms systemd-tmpfiles-setup.service
401ms console-kit-daemon.service
230ms home.mount
217ms systemd-logind.service
198ms mnt-SERVER_NYTT.mount
126ms rpcbind.service
119ms console-kit-log-system-start.service
74ms dbus.service
59ms crond.service
58ms systemd-user-sessions.service
23ms eth0-network.service
18ms dev-sda3.swap
3ms tmp.mountWhich is ok. But still a bit slower than before the systemd-tools/udev update. On the other hand, I suspect that the figures are relative, that they don't reflect the real start times.
Offline
Back to normal after a e4rat rerun.:
Startup finished in 7026ms (kernel) + 5213ms (userspace) = 12240ms
With e4rat I find that these figures are a bit skewed because it seems that e4rat's preloading gets added to the kernel figure, and not the userspace. This isn't correct in my case since I use autologin and have some apps autostart.
Offline
How do you measure your boot time?
Offline
systemd has few tools for mesuring boot time:
systemd-analyze: shows kernel and userspace boot time
systemd-analyze balme: shows what processes take most time to startup
systemd-analyze plot > /tmp/plot.svg: gives you simple bootchart as an svg
Offline
Nice, thank you. Using Linux since 8 years now and I still learn new things ![]()
Offline
Some scripts of mine;
#!/bin/bash
systemd-analyze
systemd-analyze blame
exit 0Plot and open in Firefox;
#!/bin/bash
DATE=$(date +%F-%H%M)
# DATE includes time as well
systemd-analyze plot > /home/user/$DATE-systemd-graph.svg
wait
firefox /home/user/$DATE-systemd-graph.svg
exit 0Last edited by swanson (2012-06-04 13:36:59)
Offline