Dear systemd folks,
hopefully it is alright to report my findings here. If you have any
suggestions to improve the startup time, please do not hesitate to tell
me. ;-)
Hardware
• ASRock E350M1 with dual core 1.6 GHz Fusion CPU [1]
• Crucial m4 SSD connected via SATA-3-cable [2]
• one Ext4 partition
Software
• default Debian Sid/unstable installed using `grml-debootstrap` and
Grml live system
• `aptitude purge mdadm lvm2`
• `aptitude install systemd` (version 44-1)
• `linux-image-3.2.0-2-amd64` (version 3.2.17-1)
Results
===
1. Passing `init=/bin/systemd` to the Linux kernel command line the GDM
3 login screen showed up noticeably faster.
2. GDM 3 did not list the available users though, which had to be
entered manually. After logging out again users are displayed fine.
3. Systemd says start up took 7.5 seconds.
$ systemd-analyze
Startup finished in 4077ms (kernel) + 3390ms (userspace) =
7468ms
4. All units take less than a second to start.
$ systemd-analyze blame
948ms avahi-daemon.service
729ms postfix.service
656ms rsyslog.service
632ms systemd-logind.service
559ms console-kit-log-system-start.service
523ms bootlogs.service
520ms chrony.service
467ms udev.service
451ms rc.local.service
436ms loadcpufreq.service
427ms keymap.service
424ms ssh.service
396ms cron.service
388ms dev-mqueue.mount
367ms systemd-modules-load.service
360ms sys-kernel-debug.mount
340ms udev-trigger.service
327ms systemd-sysctl.service
324ms dev-hugepages.mount
296ms sys-kernel-security.mount
281ms network-manager.service
279ms saned.service
279ms systemd-user-sessions.service
277ms gdm3.service
264ms media.mount
247ms systemd-remount-api-vfs.service
215ms pppd-dns.service
211ms resolvconf.service
199ms systemd-tmpfiles-setup.service
195ms screen-cleanup.service
191ms kbd.service
159ms networking.service
151ms console-setup.service
147ms pulseaudio.service
143ms cpufrequtils.service
91ms hdparm.service
91ms mountoverflowtmp.service
88ms keyboard-setup.service
87ms sysfsutils.service
87ms debian-fixup.service
59ms remount-rootfs.service
59ms colord-sane.service
56ms console-kit-daemon.service
48ms colord.service
44ms polkitd.service
31ms accounts-daemon.service
26ms upower.service
22ms udisks.service
19ms boot-efi.mount
13ms rtkit-daemon.service
5. Also I experience the sudo issue [3].
Conclusions
===
1. I should follow the optimization suggestions in the systemd Wiki [4].
2. Improving loading time of the Linux kernel should be my priority
right now. With four seconds it take more than half of the total Debian
startup time. I would not have expected that.
I guess I need to use `bootchart` to check if the long time is due to
the slow 1.6 GHz dual Fusion CPU or if the storage is not set up
correctly.
3. It will be interesting if GNOME 3.4 will speed up things too as
mentioned in the Wiki [4]. Currently `gnome-shell` 3.2.2.1-4+b1 is
installed.
Thank you very much for this promising piece of software,
Paul
[1] http://www.asrock.com/mb/overview.asp?Model=E350M1
[2] http://www.crucial.com/store/partspecs.aspx?imodule=CT256M4SSD2
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667470
[4] http://freedesktop.org/wiki/Software/systemd/Optimizations
signature.asc
Description: This is a digitally signed message part
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
