Post your Systemd startup times

#62

why not mask lvm2?

0 Likes

#63

Not sure how to do that.

0 Likes

#64

from the wiki systemd
Mask a unit to make it impossible to start it (both manually and as a dependency, which makes masking dangerous):

systemctl mask unit

Unmask a unit:

systemctl unmask unit

I’ve masked it and I have no problems, since I do not use lvm

1 Like

#65

Nice looks like I don’t use it either :smiley: Thanks for that.

Startup finished in 3.306s (kernel) + 2.799s (userspace) = 6.106s
graphical.target reached after 2.787s in userspace
857ms run-media-dobbie-Time\x20Machine.mount
           808ms dev-sdd1.device
           799ms dev-disk-by\x2duuid-a9de30d6\x2ddd5e\x2d47a2\x2d8af8\x2ddaf3a73266db.swap
           710ms run-media-dobbie-Movies.mount
           539ms systemd-journal-flush.service
           401ms systemd-logind.service
           401ms run-media-dobbie-Important.mount
           377ms run-media-dobbie-Music.mount
           371ms lightdm.service
           266ms systemd-hwdb-update.service
           161ms systemd-fsck@dev-disk-by\x2duuid-f50f1d01\x2dcc71\x2d4d72\x2dacb6\x2df3d7d70c2e30.service
           148ms systemd-remount-fs.service
           143ms user@1000.service
           142ms systemd-sysusers.service
           134ms home.mount
           124ms ldconfig.service
           109ms polkit.service
            82ms NetworkManager.service
            75ms systemd-udev-trigger.service
            57ms systemd-journald.service
            45ms systemd-udevd.service
            34ms systemd-random-seed.service
            34ms dnsmasq.service
            29ms dev-hugepages.mount
            28ms systemd-tmpfiles-setup.service
            27ms dev-mqueue.mount
            21ms systemd-modules-load.service
            20ms kmod-static-nodes.service
            18ms systemd-tmpfiles-setup-dev.service
1 Like

#66

Interesting thread.

Startup finished in 2.581s (kernel) + 2.482s (userspace) = 5.063s
graphical.target reached after 1.225s in userspace

lvm2-monitor-service only takes up 304ms on my notebook but I might just mask it as well because I think I do not need it, either…

0 Likes

#67

Starts and stops dmeventd monitoring for lvm2. If you are not using LVM2 (Linux volume manager) based storage disable it.

0 Likes

#68

Even you, if you do not use lvm2 you could mask it, save many seconds.

1 Like

#69

I’ll do it, thanks for the tip!

0 Likes

#70

2018-12-01-123631_645x218_scrot

Pretty fast, but I still want to shave it down some. :sweat_smile:

0 Likes

#71

Pretty fast @LionessAlana !

1 Like

#72

Thanks! I’m pretty happy with it! Not much more I can trim relly :grinning:

1 Like

#73

ThinkPad x240, i7-4600, SSD:

┌ ~
└> % systemd-analyze 12:49:50
Startup finished in 1.879s (kernel) + 2.751s (userspace) = 4.631s
graphical.target reached after 1.427s in userspace
┌ ~
└> % systemd-analyze blame 13:06:41
1.236s accounts-daemon.service
1.208s polkit.service
455ms lvm2-monitor.service
433ms systemd-fsck@dev-disk-by\x2duuid-34602a30\x2df4ce\x2d47c4\x2d86da\x2d14d7fd9320a0.serv>
303ms dev-sda6.device
157ms systemd-backlight@backlight:intel_backlight.service
147ms systemd-logind.service
94ms systemd-timesyncd.service
85ms ldconfig.service
84ms systemd-journal-flush.service
83ms NetworkManager.service
74ms udisks2.service
61ms systemd-udev-trigger.service
58ms lightdm.service
40ms systemd-journald.service
38ms systemd-udevd.service
34ms user@1000.service
31ms dev-disk-by\x2duuid-5d8bc74f\x2d4500\x2d41a2\x2d893e\x2d69630bc38792.swap
25ms systemd-tmpfiles-clean.service
19ms kmod-static-nodes.service
19ms dev-mqueue.mount
19ms sys-kernel-debug.mount
18ms systemd-sysusers.service
16ms systemd-sysctl.service
16ms sys-kernel-config.mount
16ms wpa_supplicant.service
15ms systemd-remount-fs.service
14ms systemd-tmpfiles-setup.service
14ms systemd-tmpfiles-setup-dev.service
12ms systemd-journal-catalog-update.service
10ms systemd-random-seed.service
9ms systemd-rfkill.service
9ms dev-hugepages.mount
8ms user-runtime-dir@1000.service
8ms systemd-update-utmp.service
7ms systemd-backlight@leds:tpacpi::kbd_backlight.service
6ms sys-fs-fuse-connections.mount
6ms systemd-user-sessions.service
6ms boot.mount
5ms systemd-update-done.service
5ms tmp.mount
5ms rtkit-daemon.service
lines 1-42/42 (END)

2 Likes

#74

That s pretty quick @entr0py

1 Like

#75

I am so lucky with my new thinkpad as well as with ArchLabs <3

0 Likes

#76

Great, what s the model that you have @entr0py , usually Thinkpads are pretty good with Linux.

0 Likes

#77

I don’t really know, @altman. It’s a X240 Ultrabook (?) with i7-4600U , 8GB RAM and a 256GB SSD.
I used a ThinkPad e145 before, but it died from shame because I was to lazy to install a proper OS and going crazy by using Windows 10.
So now I have a real nice Laptop and just fell in love with ArchLabs, maybe the best distro I ever seen :wink:

0 Likes

#78

That s great, glad that you like your laptop.

0 Likes

#79

It seems to boot faster with every kernel update:

-> % systemd-analyze 13:08:09
Startup finished in 1.591s (kernel) + 1.310s (userspace) = 2.902s
graphical.target reached after 1.310s in userspace

0 Likes

#80

My slowmo HP BL Testing install;

systemd-analyze
Startup finished in 4.287s (kernel) + 1min 23.384s (userspace) = 1min 27.671s
graphical.target reached after 32.943s in userspace

0 Likes

#81

^ Not as slow as my Debian buster system (ThinkPad X201, 4GiB RAM, Kingston SV300 128 GiB SSD):

empty@shinken:~ $ systemd-analyze                                                         
Startup finished in 4.764s (kernel) + 2min 1.517s (userspace) = 2min 6.281s 
graphical.target reached after 2min 1.498s in userspace
empty@shinken:~ $ systemd-analyze blame --no-p                                            
      2min 161ms systemd-networkd-wait-online.service
          2.210s dev-sda3.device
           796ms systemd-hwdb-update.service
           755ms systemd-resolved.service
           350ms nftables.service
           318ms systemd-journald.service
           306ms keyboard-setup.service
           285ms systemd-udev-trigger.service
           241ms systemd-logind.service
           147ms systemd-networkd.service
           143ms systemd-timesyncd.service
           115ms user@1000.service
            95ms apparmor.service
            73ms systemd-remount-fs.service
            69ms lm-sensors.service
            67ms systemd-user-sessions.service
            65ms sys-kernel-debug.mount
            63ms atd.service
            59ms systemd-sysusers.service
            57ms systemd-tmpfiles-setup-dev.service
            53ms systemd-sysctl.service
            53ms binfmt-support.service
            48ms systemd-tmpfiles-setup.service
            46ms systemd-journal-flush.service
            43ms systemd-modules-load.service
            41ms kmod-static-nodes.service
            40ms console-setup.service
            38ms systemd-udevd.service
            35ms dev-mqueue.mount
            35ms systemd-random-seed.service
            33ms dev-hugepages.mount
            32ms dev-disk-by\x2duuid-c5798041\x2dc961\x2d4189\x2daa94\x2db929c917528f.swap
            31ms proc-sys-fs-binfmt_misc.mount
            31ms hddtemp.service
            29ms systemd-rfkill.service
            24ms systemd-backlight@backlight:intel_backlight.service
            24ms systemd-update-utmp.service
            18ms user-runtime-dir@1000.service
            18ms systemd-backlight@backlight:acpi_video0.service
            15ms alsa-restore.service
            14ms systemd-update-utmp-runlevel.service
empty@shinken:~ $

:slightly_frowning_face:

I think systemd-networkd is being very conservative about network.target though, I have automatic login & automatic startx configured and it gets me to the desktop ~16 seconds after I select the GRUB menu entry.

1 Like