Page 4 of 5 FirstFirst ... 2345 LastLast
Results 31 to 40 of 44

Thread: TW boot times vs. 15.2/15.3 times & wickedd*

  1. #31
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,508
    Blog Entries
    1

    Default Re: TW boot times vs. 15.2/15.3 times & wickedd*

    Quote Originally Posted by mrmazda View Post
    Enabling systemd-networkd-wait-online.service speeded up systemd-networkd to about the same speed as 15.2, more than twice the time of TW using wicked in post #26 reaching multi-user: ...My experience with TW on this host so far seems to suggest enabling nmb creates a preference for Wicked over Networkd for maximum boot to multi-user speed.
    Obviously nmd.service doesn't care about network-online.target, but waits until the daemon is ready:


    Code:
    erlangen:~ # systemd-analyze critical-chain smb.service                          
    The time when unit became active or started is printed after the "@" character. 
    The time the unit took to start is printed after the "+" character. 
    
     └─network-online.target @624ms 
      └─network.target @624ms 
        └─systemd-resolved.service @465ms +158ms
          └─systemd-tmpfiles-setup.service @441ms +22ms
            └─systemd-journal-flush.service @253ms +186ms
              └─var.mount @243ms +8ms
                └─local-fs-pre.target @236ms 
                  └─systemd-tmpfiles-setup-dev.service @225ms +10ms
                    └─kmod-static-nodes.service @210ms +7ms
                      └─systemd-journald.socket 
                        └─system.slice 
                          └─-.slice 
    erlangen:~ #
    Code:
    erlangen:~ # journalctl -b 0 _PID=758 -o short-monotonic  
    -- Logs begin at Fri 2021-02-19 13:01:26 CET, end at Mon 2021-03-22 07:58:04 CET. -- 
    [    4.007774] erlangen nmbd[758]: [2021/03/22 07:47:01.161538,  0] ../../lib/util/become_daemon.c:166(daemon_status)
    [    4.008019] erlangen nmbd[758]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
    [    4.008077] erlangen nmbd[758]: [2021/03/22 07:47:01.161574,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
    [    4.008117] erlangen nmbd[758]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
    [   14.004500] erlangen nmbd[758]: [2021/03/22 07:47:11.162464,  0] ../../lib/util/become_daemon.c:152(daemon_ready)
    [   14.004791] erlangen nmbd[758]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
    [   37.122727] erlangen nmbd[758]: [2021/03/22 07:47:34.280552,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
    [   37.123491] erlangen nmbd[758]:   *****
    [   37.123650] erlangen nmbd[758]:  
    [   37.123765] erlangen nmbd[758]:   Samba name server ERLANGEN is now a local master browser for workgroup WORKGROUP on subnet 192.168.178.24
    [   37.123913] erlangen nmbd[758]:  
    [   37.124013] erlangen nmbd[758]:   *****
    erlangen:~ #
    However this behavior won't delay other services, such as display-manager.service.

    Code:
    erlangen:~ # systemd-analyze critical-chain display-manager.service                       
    The time when unit became active or started is printed after the "@" character. 
    The time the unit took to start is printed after the "+" character. 
    
    display-manager.service +688ms
    └─apache2.service @702ms +131ms
      └─time-sync.target @699ms 
        └─chronyd.service @625ms +73ms
          └─nss-lookup.target @624ms 
            └─systemd-resolved.service @465ms +158ms
              └─systemd-tmpfiles-setup.service @441ms +22ms
                └─systemd-journal-flush.service @253ms +186ms
                  └─var.mount @243ms +8ms
                    └─local-fs-pre.target @236ms 
                      └─systemd-tmpfiles-setup-dev.service @225ms +10ms
                        └─kmod-static-nodes.service @210ms +7ms
                          └─systemd-journald.socket 
                            └─system.slice 
                              └─-.slice 
    erlangen:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  2. #32
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,508
    Blog Entries
    1

    Default Re: TW boot times vs. 15.2/15.3 times & wickedd*

    More smb startup:

    Code:
    3400G:~ # systemd-analyze critical-chain                               
    The time when unit became active or started is printed after the "@" character. 
    The time the unit took to start is printed after the "+" character. 
    
    graphical.target @4.035s 
    └─multi-user.target @4.035s 
      └─smb.service @3.947s +87ms
        └─nmb.service @3.825s +119ms
          └─network-online.target @3.819s 
            └─systemd-networkd-wait-online.service @519ms +3.299s
              └─systemd-networkd.service @457ms +61ms
                └─systemd-udevd.service @358ms +96ms
                  └─systemd-tmpfiles-setup-dev.service @341ms +8ms
                    └─kmod-static-nodes.service @290ms +33ms
                      └─systemd-journald.socket 
                        └─-.mount 
                          └─system.slice 
                            └─-.slice 
    3400G:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  3. #33
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,818
    Blog Entries
    1

    Default Re: TW boot times vs. 15.2/15.3 times & wickedd*

    Here's from a fresh quite minimal 15.3b0315 installation (which resulted in me filing two new bug reports[1]), before enabling nmb:
    Code:
    # systemd-analyze critical-chain
    ...
    multi-user.target @2.798s
    └─kbdsettings.service @683ms +2.113s
      └─basic.target @672ms
        └─sockets.target @671ms
          └─dbus.socket @670ms
            └─sysinit.target @666ms
              └─systemd-udevd.service @331ms +334ms
                └─systemd-tmpfiles-setup-dev.service @300ms +19ms
                  └─kmod-static-nodes.service @255ms +17ms
                    └─systemd-journald.socket
                      └─-.mount
                        └─system.slice
                          └─-.slice
    # systemd-analyze blame
    2.113s kbdsettings.service
     868ms dracut-initqueue.service
     543ms systemd-networkd.service
    ...
    After doing nothing but enabling nmb, smb and systemd-networkd-wait-online, then rebooting:
    Code:
    # systemd-analyze critical-chain
    ...
    multi-user.target @11.388s
    └─smb.service @11.273s +112ms
      └─nmb.service @1.151s +10.118s
        └─network.target @1.148s
          └─systemd-networkd.service @689ms +455ms
            └─systemd-udevd.service @308ms +358ms
              └─systemd-tmpfiles-setup-dev.service @279ms +15ms
                └─kmod-static-nodes.service @241ms +15ms
                  └─systemd-journald.socket
                    └─system.slice
                      └─-.slice
    # systemd-analyze blame
    10.118s nmb.service
     2.096s kbdsettings.service
      900ms dracut-initqueue.service
      455ms systemd-networkd.service
    ...
    systemd-networkd-wait-online didn't show up in blame or critical-chain.

    [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1183886
    https://bugzilla.opensuse.org/show_bug.cgi?id=1183887
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.2, +TW, 15.1, 15.0 & 13.1 on Haswell
    Secondary: eComStation (OS/2) &15.1 on i965P w/ Radeon
    Tertiary: Mageia,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&&&

  4. #34
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,818
    Blog Entries
    1

    Default Re: TW boot times vs. 15.2/15.3 times & wickedd*

    I'm perplexed by by a discovery after another TW conversion from wicked to networkd. This is an old 3.0GHz Core2Duo with storage only on 1 SSD. Boot is slower with systemd-networkd-wait-online disabled than with it enabled. With it disabled, nmb takes longer to startup, the critical chain has more elements, and total startup time is 33% longer/slower:
    Disabled:
    Code:
    # systemd-analyze critical-chain
    ...
    multi-user.target @7.608s
    └─smb.service @7.472s +135ms
      └─nmb.service @1.952s +5.518s
        └─basic.target @1.853s
          └─sockets.target @1.849s
            └─telnet.socket @1.828s
              └─sysinit.target @1.752s
                └─systemd-update-utmp.service @1.719s +30ms
                  └─systemd-tmpfiles-setup.service @1.514s +163ms
                    └─local-fs.target @1.388s
                      └─home.mount @1.086s +242ms
                        └─systemd-fsck@dev-disk-by\x2dlabel-08home.service @880ms +196ms
                          └─local-fs-pre.target @805ms
                            └─systemd-tmpfiles-setup-dev.service @740ms +61ms
                              └─kmod-static-nodes.service @583ms +98ms
                                └─systemd-journald.socket
                                  └─-.mount
                                    └─system.slice
                                      └─-.slice
    # systemd-analyze blame | head -n4
    5.518s nmb.service                                          
    2.057s kbdsettings.service                                  
    1.827s systemd-random-seed.service                          
     702ms initrd-switch-root.service
    Enabled:
    Code:
    # systemd-analyze critical-chain
    ...
    multi-user.target @5.707s
    └─smb.service @5.556s +150ms
      └─nmb.service @5.403s +151ms
        └─network-online.target @5.401s
          └─systemd-networkd-wait-online.service @2.339s +3.061s
            └─systemd-networkd.service @1.795s +472ms
              └─systemd-udevd.service @1.411s +58ms
                └─systemd-hwdb-update.service @740ms +667ms
                  └─systemd-remount-fs.service @656ms +63ms
                    └─systemd-fsck-root.service @584542y 2w 2d 20h 1min 48.791s +27ms
                      └─systemd-journald.socket
                        └─-.mount
                          └─system.slice
                            └─-.slice
    # systemd-analyze blame | head -n4
    3.061s systemd-networkd-wait-online.service                 
    2.121s kbdsettings.service                                  
    1.785s systemd-random-seed.service                          
     725ms initrd-switch-root.service


    Also, the faster of the two takes close to twice as long to reach multi-user as Debian 10.
    Code:
    ...
    └─multi-user.target @2.931s
      └─smbd.service @2.583s +347ms
        └─nmbd.service @2.237s +344ms
          └─basic.target @2.221s
            └─sockets.target @2.221s
              └─dbus.socket @2.221s
                └─sysinit.target @2.218s
                  └─systemd-update-utmp.service @2.045s +17ms
                    └─systemd-tmpfiles-setup.service @2.008s +34ms
                      └─local-fs.target @2.001s
                        └─home.mount @1.942s +58ms
                          └─systemd-fsck@dev-disk-by\x2dlabel-08home.service @1.667s +274ms
                            └─dev-disk-by\x2dlabel-08home.device @1.655s
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.2, +TW, 15.1, 15.0 & 13.1 on Haswell
    Secondary: eComStation (OS/2) &15.1 on i965P w/ Radeon
    Tertiary: Mageia,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&&&

  5. #35
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,508
    Blog Entries
    1

    Default Tumbleweed vs. Kubuntu

    Kubuntu, default packages, NetworkManager:
    Code:
    3400G:~ # journalctl --directory /mnt/var/log/journal/ -b --grep Reached -o short-monotonic --quiet  
    [    3.438598] Ubuntu systemd[1]: Reached target User and Group Name Lookups. 
    [    3.438619] Ubuntu systemd[1]: Reached target Remote File Systems. 
    [    3.438632] Ubuntu systemd[1]: Reached target Slices. 
    [    3.499670] Ubuntu systemd[1]: Reached target Local File Systems (Pre). 
    [    3.504417] Ubuntu systemd[1]: Reached target Swap. 
    [    3.643233] Ubuntu systemd[1]: Reached target Local Encrypted Volumes. 
    [    4.868404] Ubuntu systemd[1]: Reached target Local File Systems. 
    [    4.982071] Ubuntu systemd[1]: Reached target System Time Set. 
    [    4.982180] Ubuntu systemd[1]: Reached target System Time Synchronized. 
    [    4.993685] Ubuntu systemd[1]: Reached target System Initialization. 
    [    4.996497] Ubuntu systemd[1]: Reached target Paths. 
    [    4.996564] Ubuntu systemd[1]: Reached target Timers. 
    [    4.999603] Ubuntu systemd[1]: Reached target Host and Network Name Lookups. 
    [    4.999669] Ubuntu systemd[1]: Reached target Sockets. 
    [    4.999735] Ubuntu systemd[1]: Reached target Basic System. 
    [    5.017166] Ubuntu systemd[1]: Reached target Login Prompts. 
    [    5.054161] Ubuntu systemd[1]: Reached target Sound Card. 
    [    5.188570] Ubuntu systemd[1]: Reached target Network. 
    [    6.599277] Ubuntu systemd[1040]: Reached target Paths. 
    [    6.599945] Ubuntu systemd[1040]: Reached target Timers. 
    [    6.608298] Ubuntu systemd[1040]: Reached target Sockets. 
    [    6.608488] Ubuntu systemd[1040]: Reached target Basic System. 
    [    7.610727] Ubuntu systemd[1040]: Reached target Main User Target.
    [   11.553886] Ubuntu systemd[1]: Reached target Network is Online. 
    [   11.570827] Ubuntu systemd[1]: Reached target Multi-User System. 
    [   11.570946] Ubuntu systemd[1]: Reached target Graphical Interface. 
    3400G:~ #
    Tumbleweed, default packages, NetworkManager:

    Code:
    3400G:~ # journalctl --directory /mnt/@/var/log/journal/ -b --grep Reached -o short-monotonic --quiet 
    [    3.159924] localhost systemd[1]: Reached target Local File Systems.
    [    3.159959] localhost systemd[1]: Reached target Slices.
    [    3.159971] localhost systemd[1]: Reached target Swap.
    [    3.159982] localhost systemd[1]: Reached target Timers.
    [    3.160284] localhost systemd[1]: Reached target Sockets.
    [    4.230793] localhost systemd[1]: Reached target System Initialization.
    [    4.246697] localhost systemd[1]: Reached target Paths.
    [    4.246738] localhost systemd[1]: Reached target Basic System.
    [    4.379829] localhost systemd[1]: Reached target Initrd Root Device.
    [    5.039204] localhost systemd[1]: Reached target Remote File Systems (Pre).
    [    5.039255] localhost systemd[1]: Reached target Remote File Systems.
    [    5.073722] localhost systemd[1]: Reached target Initrd Root File System.
    [    5.251327] localhost systemd[1]: Reached target Initrd File Systems.
    [    5.251356] localhost systemd[1]: Reached target Initrd Default Target.
    [    5.281563] localhost systemd[1]: Reached target Switch Root.
    [    5.674363] 3400G-test systemd[1]: Reached target Remote File Systems.
    [    5.674388] 3400G-test systemd[1]: Reached target Slices.
    [    5.674415] 3400G-test systemd[1]: Reached target Swap.
    [    5.674442] 3400G-test systemd[1]: Reached target System Time Set.
    [    5.681761] 3400G-test systemd[1]: Reached target Local Encrypted Volumes.
    [    5.708043] 3400G-test systemd[1]: Reached target Local File Systems (Pre).
    [    5.854127] 3400G-test systemd[1]: Reached target Local File Systems.
    [    5.899723] 3400G-test systemd[1]: Reached target System Initialization.
    [    5.910712] 3400G-test systemd[1]: Reached target Paths.
    [    5.912584] 3400G-test systemd[1]: Reached target Sockets.
    [    5.912668] 3400G-test systemd[1]: Reached target Basic System.
    [    5.963938] 3400G-test systemd[1]: Reached target Host and Network Name Lookups.
    [    5.964034] 3400G-test systemd[1]: Reached target User and Group Name Lookups.
    [    6.455746] 3400G-test systemd[1]: Reached target Sound Card.
    [    6.544733] 3400G-test systemd[1]: Reached target Network (Pre).
    [    6.581098] 3400G-test systemd[1]: Reached target Network.
    [    6.621694] 3400G-test systemd[1]: Reached target System Time Synchronized.
    [    6.623479] 3400G-test systemd[1]: Reached target Timers.
    [    6.779528] 3400G-test systemd[1]: Reached target Login Prompts.
    [    7.204826] 3400G-test systemd[1]: Reached target Multi-User System.
    [    7.289241] 3400G-test systemd[1]: Reached target Graphical Interface.
    3400G:~ #
    Tumbleweed, usable system, systemd-networkd, additional packages installed:

    Code:
    3400G:~ # journalctl -b --grep Reached -o short-monotonic --quiet                                    
    [    2.144895] 3400G systemd[1]: Reached target Local File Systems. 
    [    2.146252] 3400G systemd[1]: Reached target Slices. 
    [    2.147536] 3400G systemd[1]: Reached target Swap. 
    [    2.148808] 3400G systemd[1]: Reached target Timers. 
    [    2.155261] 3400G systemd[1]: Reached target Sockets. 
    [    3.260809] 3400G systemd[1]: Reached target System Initialization. 
    [    3.278160] 3400G systemd[1]: Reached target Paths. 
    [    3.278188] 3400G systemd[1]: Reached target Basic System. 
    [    3.409461] 3400G systemd[1]: Reached target Initrd Root Device. 
    [    4.007104] 3400G systemd[1]: Reached target Remote File Systems (Pre). 
    [    4.007160] 3400G systemd[1]: Reached target Remote File Systems. 
    [    4.039776] 3400G systemd[1]: Reached target Initrd Root File System. 
    [    4.209844] 3400G systemd[1]: Reached target Initrd File Systems. 
    [    4.209875] 3400G systemd[1]: Reached target Initrd Default Target. 
    [    4.262326] 3400G systemd[1]: Reached target Switch Root. 
    [    4.738461] 3400G systemd[1]: Reached target Remote File Systems. 
    [    4.738484] 3400G systemd[1]: Reached target Slices. 
    [    4.738509] 3400G systemd[1]: Reached target Swap. 
    [    4.738529] 3400G systemd[1]: Reached target System Time Set. 
    [    4.745394] 3400G systemd[1]: Reached target Local Encrypted Volumes. 
    [    4.770775] 3400G systemd[1]: Reached target Local File Systems (Pre). 
    [    4.951749] 3400G systemd[1]: Reached target Local File Systems. 
    [    4.999262] 3400G systemd[1]: Reached target System Initialization. 
    [    5.000335] 3400G systemd[1]: Reached target Paths. 
    [    5.003047] 3400G systemd[1]: Reached target Sockets. 
    [    5.003198] 3400G systemd[1]: Reached target Basic System. 
    [    5.210190] 3400G systemd[1]: Reached target Network.
    [    5.210307] 3400G systemd[1]: Reached target Network is Online. 
    [    5.210408] 3400G systemd[1]: Reached target Host and Network Name Lookups. 
    [    5.278180] 3400G systemd[1]: Reached target System Time Synchronized. 
    [    5.281921] 3400G systemd[1]: Reached target Timers. 
    [    5.575209] 3400G systemd[1]: Reached target Login Prompts. 
    [    5.590261] 3400G systemd[1]: Reached target Sound Card. 
    [    5.757123] 3400G systemd[1]: Reached target Multi-User System. 
    [    6.082268] 3400G systemd[1]: Reached target Graphical Interface. 
    3400G:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  6. #36
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,818
    Blog Entries
    1

    Default Re: Tumbleweed vs. Kubuntu

    Quote Originally Posted by karlmistelberger View Post
    Code:
    Kubuntu, default packages, NetworkManager:
    ...
    [    4.999735] Ubuntu systemd[1]: Reached target Basic System. 
    ...
    [    5.188570] Ubuntu systemd[1]: Reached target Network. 
    ...
    Tumbleweed, default packages, NetworkManager:
    ...
    [    4.246738] localhost systemd[1]: Reached target Basic System.
    ...
    [    6.581098] 3400G-test systemd[1]: Reached target Network.
    ...
    Tumbleweed, usable system, systemd-networkd, additional packages installed:
    ...
    [    3.278188] 3400G systemd[1]: Reached target Basic System. 
    ...
    [    5.210190] 3400G systemd[1]: Reached target Network.
    ...
    If there's an answer to any question I asked in your response, it's totally escaping my grasp.

    If any of the font markup is supposed to help, I won't know about it except as markup in composing a reply. My user stylesheet for this forum limits colors to #000 on #FFF (black on white). Similar for fonts - code-tagged is "monospace", all other is "sans-serif", and attempts to size fonts are ignored (only CSS medium is ever displayed). Bold and italic are allowed.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.2, +TW, 15.1, 15.0 & 13.1 on Haswell
    Secondary: eComStation (OS/2) &15.1 on i965P w/ Radeon
    Tertiary: Mageia,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&&&

  7. #37
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,508
    Blog Entries
    1

    Default Re: Tumbleweed vs. Kubuntu

    Quote Originally Posted by mrmazda View Post
    If there's an answer to any question I asked in your response, it's totally escaping my grasp.
    Short answer: YMMV.

    Longer answer: For a quick guess, systemd-analyze is fine. However you always need to look at the details. Watch for botched install sections, dependencies, ordering, unneeded services and many more. Target reached time helps to spot problems. See also systemctl list-dependencies ...target.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  8. #38
    Join Date
    Feb 2009
    Location
    New Zealand
    Posts
    174

    Default Re: TW boot times vs. 15.2/15.3 times & wickedd*

    Quote Originally Posted by mrmazda View Post
    I'm perplexed by by a discovery after another TW conversion from wicked to networkd. This is an old 3.0GHz Core2Duo with storage only on 1 SSD. Boot is slower with systemd-networkd-wait-online disabled than with it enabled. With it disabled, nmb takes longer to startup, the critical chain has more elements, and total startup time is 33% longer/slower:
    ...
    I found the same, switching away from wicked made the delay much worse.

    I also found that the source code of nmbd contains hard coded sleep-5-seconds which kick in if the network is unavailable at startup. It may well be that these kick in if nmbd starts too early, and may then cause further delays - which might play some role with the networkd experience.

    I also had a play with changing the sleep durations and rebuilding nmbd - with no luck.

    I subsequently raised a bug where I've summarized my experiments: https://bugzilla.opensuse.org/show_bug.cgi?id=1183148 This bug which has now been closed as fixed, so it will be interesting to see if there is any improvement.

  9. #39
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,508
    Blog Entries
    1

    Default Re: TW boot times vs. 15.2/15.3 times & wickedd*

    Quote Originally Posted by mchnz View Post
    I found the same, switching away from wicked made the delay much worse.
    nmb won't allow cheating with network-online.target. With systemd-networkd managing the links systemd-networkd-wait-online.service needs to be enabled:

    Code:
    3400G:~ # systemctl status systemd-networkd-wait-online.service                   
     systemd-networkd-wait-online.service - Wait for Network to be Configured 
         Loaded: loaded (/usr/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: disabled) 
         Active: active (exited) since Tue 2021-04-13 06:35:39 CEST; 7min ago 
           Docs: man:systemd-networkd-wait-online.service(8) 
        Process: 601 ExecStart=/usr/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS) 
       Main PID: 601 (code=exited, status=0/SUCCESS) 
            CPU: 9ms 
    
    Apr 13 06:35:37 3400G systemd[1]: Starting Wait for Network to be Configured... 
    Apr 13 06:35:39 3400G systemd[1]: Finished Wait for Network to be Configured. 
    3400G:~ #

    Code:
    3400G:~ # systemd-analyze critical-chain                        
    The time when unit became active or started is printed after the "@" character. 
    The time the unit took to start is printed after the "+" character. 
    
    graphical.target @3.414s 
    └─multi-user.target @3.414s 
      └─nmb.service @3.275s +138ms
        └─network-online.target @3.273s 
          └─systemd-networkd-wait-online.service @549ms +2.723s
            └─systemd-networkd.service @482ms +66ms
              └─systemd-udevd.service @370ms +110ms
                └─systemd-tmpfiles-setup-dev.service @349ms +11ms
                  └─kmod-static-nodes.service @333ms +8ms
                    └─systemd-journald.socket 
                      └─system.slice 
                        └─-.slice 
    3400G:~ #
    Disabling systemd-networkd-wait-online.service results in nmb.service waiting repeatedly 5 seconds until network is configured.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  10. #40
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,818
    Blog Entries
    1

    Default Re: TW boot times vs. 15.2/15.3 times & wickedd*

    This is first boot of a fresh minimalist 15.3RC, before enabling samba or switching from Wicked to Systemd-Networkd:
    Code:
    └─multi-user.target @6.658s
      └─chronyd.service @6.605s +51ms
        └─network.target @6.604s
          └─wicked.service @2.394s +4.209s
            └─wickedd-nanny.service @2.368s +24ms
              └─wickedd.service @2.315s +51ms
                └─wickedd-auto4.service @2.257s +56ms
                  └─dbus.service @2.238s
                    └─basic.target @2.236s
                      └─sockets.target @2.235s
                        └─dbus.socket @2.234s
                          └─sysinit.target @2.232s
                            └─systemd-udev-settle.service @521ms +1.711s
                              └─systemd-udev-trigger.service @342ms +176ms
                                └─systemd-udevd-kernel.socket @302ms
                                  └─system.slice
                                    └─-.slice
    4.209s wicked.service                        
    1.711s systemd-udev-settle.service           
     961ms dracut-initqueue.service              
     438ms systemd-hwdb-update.service           
     405ms initrd-switch-root.service            
     387ms systemd-journald.service              
     337ms systemd-logind.service                
     326ms systemd-udevd.service                 
     194ms initrd-parse-etc.service              
     176ms systemd-udev-trigger.service          
     163ms user@0.service                        
     150ms kbdsettings.service                   
     101ms smartd.service                        
      83ms modprobe@drm.service                  
      82ms sysroot.mount                         
      71ms modprobe@configfs.service             
      69ms modprobe@fuse.service                 
      62ms systemd-modules-load.service          
      59ms sys-kernel-tracing.mount              
      58ms kmod-static-nodes.service             
      58ms dev-hugepages.mount                   
      57ms dev-mqueue.mount
    Same 15.3 after switching to Systemd-Networkd and disabling systemd-udev-settle:
    Code:
    # inxi -SCy
    System:
      Host: ab85m Kernel: 5.3.18-56-default x86_64 bits: 64 
      Console: tty pts/0 (vt 3) Distro: openSUSE Leap 15.3 
    CPU:
      Info: Dual Core model: Intel Pentium G3220 bits: 64 type: MCP  arch: Haswell
      Speed: 2375 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 2375 2: 2381 
    # systemd-analyze critical-chain
    └─multi-user.target @3.043s
      └─kbdsettings.service @921ms +2.121s
        └─basic.target @915ms
          └─sockets.target @915ms
            └─dbus.socket @914ms
              └─sysinit.target @913ms
                └─systemd-udevd.service @522ms +390ms
                  └─systemd-tmpfiles-setup-dev.service @443ms +39ms
                    └─kmod-static-nodes.service @334ms +66ms
                      └─systemd-journald.socket
                        └─-.mount
                          └─system.slice
                            └─-.slice
    # systemd-analyze blame head
    2.121s kbdsettings.service                                 
    1.241s systemd-networkd.service                            
     964ms dracut-initqueue.service                            
     768ms systemd-logind.service                              
     441ms initrd-switch-root.service                          
     439ms systemd-journald.service                            
     390ms systemd-udevd.service                               
     212ms initrd-parse-etc.service                            
     168ms user@0.service                                      
     167ms smartd.service                                      
     155ms systemd-udev-trigger.service                        
     154ms systemd-fsck@dev-disk-by\x2dlabel-tg1p06pub.service 
     152ms systemd-fsck@dev-disk-by\x2dlabel-tg1p04usrl.service
     152ms systemd-fsck@dev-disk-by\x2dlabel-tg1p05home.service
     149ms systemd-fsck@dev-disk-by\x2dlabel-tg1p03res.service 
     146ms sshd.service                                        
     108ms modprobe@drm.service                                
      91ms sysroot.mount                                       
      71ms modprobe@fuse.service                               
      69ms boot-efi.mount                                      
      67ms sys-kernel-debug.mount                              
      67ms sys-kernel-tracing.mount
    Nice increase in boot speed, 45.7% of previous time.

    This is after enabling Samba too:
    Code:
    # systemd-analyze critical-chain
    └─multi-user.target @7.256s
      └─smb.service @7.157s +98ms
        └─nmb.service @1.820s +5.335s
          └─network.target @1.807s
            └─systemd-networkd.service @961ms +845ms
              └─systemd-udevd.service @516ms +426ms
                └─systemd-tmpfiles-setup-dev.service @425ms +35ms
                  └─kmod-static-nodes.service @325ms +63ms
                    └─systemd-journald.socket
                      └─-.mount
                        └─system.slice
                          └─-.slice
    # systemd-analyze blame head
    5.335s nmb.service                                         
    2.103s kbdsettings.service                                 
    1.051s systemd-logind.service                              
     995ms dracut-initqueue.service                            
     845ms systemd-networkd.service                            
     426ms systemd-udevd.service                               
     425ms initrd-switch-root.service                          
     408ms systemd-journald.service                            
     330ms sshd.service                                        
     273ms chronyd.service                                     
     209ms initrd-parse-etc.service                            
     180ms smartd.service                                      
     171ms systemd-udev-trigger.service                        
     170ms systemd-fsck@dev-disk-by\x2dlabel-tg1p04usrl.service
     170ms systemd-fsck@dev-disk-by\x2dlabel-tg1p05home.service
     169ms systemd-fsck@dev-disk-by\x2dlabel-tg1p06pub.service 
     166ms systemd-fsck@dev-disk-by\x2dlabel-tg1p03res.service 
     165ms user@0.service                                      
     121ms boot-efi.mount                                      
     100ms sysroot.mount                                       
      98ms smb.service                                         
      97ms systemd-sysctl.service
    138% longer to boot with Samba enabled.

    Same PC booted to TW, with networkd and samba:
    Code:
    # systemd-analyze critical-chain
    ...
    multi-user.target @4.654s
    └─smb.service @4.551s +103ms
      └─nmb.service @4.466s +83ms
        └─network-online.target @4.463s
          └─systemd-networkd-wait-online.service @1.021s +3.440s
            └─systemd-networkd.service @856ms +164ms
              └─systemd-udevd.service @606ms +248ms
                └─systemd-tmpfiles-setup-dev.service @486ms +87ms
                  └─kmod-static-nodes.service @407ms +21ms
                    └─systemd-journald.socket
                      └─-.mount
                        └─system.slice
                          └─-.slice
    # systemd-analyze blame | head -n22
    3.440s systemd-networkd-wait-online.service                
    2.070s kbdsettings.service                                 
     575ms dracut-initqueue.service                            
     559ms initrd-switch-root.service                          
     511ms systemd-journal-flush.service                       
     444ms cups.service                                        
     386ms smartd.service                                      
     373ms issue-generator.service                             
     358ms systemd-logind.service                              
     280ms chronyd.service                                     
     248ms systemd-udevd.service                               
     202ms systemd-fsck@dev-disk-by\x2dlabel-tg1p04usrl.service
     202ms systemd-fsck@dev-disk-by\x2dlabel-tg1p05home.service
     193ms systemd-fsck@dev-disk-by\x2dlabel-tg1p06pub.service 
     193ms sshd.service                                        
     190ms initrd-parse-etc.service                            
     179ms systemd-fsck@dev-disk-by\x2dlabel-tg1p03res.service 
     171ms user@0.service                                      
     164ms systemd-networkd.service                            
     112ms systemd-udev-trigger.service                        
     103ms smb.service                                         
      93ms modprobe@drm.service
    # hdparm -t /dev/sda:...519.89 MB/sec
    64.1% of equivalent 15.3.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.2, +TW, 15.1, 15.0 & 13.1 on Haswell
    Secondary: eComStation (OS/2) &15.1 on i965P w/ Radeon
    Tertiary: Mageia,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&&&

Page 4 of 5 FirstFirst ... 2345 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •