| 1 |
Greetings fellow Gentooistas, |
| 2 |
|
| 3 |
I am looking for input on how to speed up my boot process with systemd |
| 4 |
on Gentoo. |
| 5 |
|
| 6 |
First of one word to systemd: Gentoo is about choice, and I choose to |
| 7 |
take a deeper look into systemd out of curiosity, so please respect that |
| 8 |
and don't turn it into another kind of "OpenRC vs. systemd" debate. |
| 9 |
Thanks in advance. |
| 10 |
|
| 11 |
Having said that, now to my setup: I am running the vanilla kernel |
| 12 |
3.13.6 with only the necessary drivers builtin to the kernel, almost |
| 13 |
nothing as module. |
| 14 |
|
| 15 |
Features I don't need are disabled. |
| 16 |
|
| 17 |
Readahead-Services are disabled. Since my root partition is XFS, fsckd |
| 18 |
is disabled. |
| 19 |
|
| 20 |
systemd-analyze says: |
| 21 |
|
| 22 |
Startup finished in 584542y 2w 2d 20h 1min 35.953s (loader) + 1.477s |
| 23 |
(kernel) + 15.966s (userspace) = 17.444s |
| 24 |
|
| 25 |
Blame says: |
| 26 |
|
| 27 |
1min 7.815s systemd-tmpfiles-clean.service |
| 28 |
4.900s NetworkManager.service |
| 29 |
3.214s systemd-logind.service |
| 30 |
2.585s lightdm.service |
| 31 |
2.373s systemd-vconsole-setup.service |
| 32 |
1.506s systemd-update-utmp.service |
| 33 |
919ms upower.service |
| 34 |
697ms polkit.service |
| 35 |
387ms systemd-udev-trigger.service |
| 36 |
381ms systemd-sysctl.service |
| 37 |
374ms tmp.mount |
| 38 |
359ms udisks2.service |
| 39 |
334ms kmod-static-nodes.service |
| 40 |
333ms user@×.service |
| 41 |
332ms systemd-user-sessions.service |
| 42 |
299ms systemd-tmpfiles-setup-dev.service |
| 43 |
288ms sys-fs-fuse-connections.mount |
| 44 |
287ms systemd-remount-fs.service |
| 45 |
228ms systemd-tmpfiles-setup.service |
| 46 |
178ms systemd-random-seed.service |
| 47 |
117ms systemd-fsck-root.service |
| 48 |
103ms systemd-journal-flush.service |
| 49 |
71ms wpa_supplicant.service |
| 50 |
65ms accounts-daemon.service |
| 51 |
51ms user@××××.service |
| 52 |
35ms systemd-udevd.service |
| 53 |
22ms alsa-restore.service |
| 54 |
|
| 55 |
Critical Chain says: |
| 56 |
|
| 57 |
The time after the unit is active or started is printed after the "@" |
| 58 |
character. |
| 59 |
The time the unit takes to start is printed after the "+" character. |
| 60 |
|
| 61 |
graphical.target @15.965s |
| 62 |
└─multi-user.target @15.965s |
| 63 |
└─NetworkManager.service @11.065s +4.900s |
| 64 |
└─basic.target @11.065s |
| 65 |
└─timers.target @11.064s |
| 66 |
└─systemd-tmpfiles-clean.timer @11.043s |
| 67 |
└─sysinit.target @4.264s |
| 68 |
└─systemd-vconsole-setup.service @1.891s +2.373s |
| 69 |
└─systemd-journald.socket @1.572s |
| 70 |
└─-.mount @1.571s |
| 71 |
└─system.slice @1.947s |
| 72 |
└─-.slice @1.947s |
| 73 |
|
| 74 |
Boot disk is a normal HDD SATA. |
| 75 |
|
| 76 |
GDM-Replacement is lightdm. |
| 77 |
|
| 78 |
So i wonder what could I do to speedup the boot process any further? |
| 79 |
|
| 80 |
Thanks in advance. |
Archives