OpenSuse 13.2 64bit KDE speeding up boot/shutdown

Hello everyone, I have been using different distributions of Linux since last summer and I have decided to stick with OpenSuse after trying 13.1. I decided with this distribution for its’ stability which I have been looking for a long time.

Besides network roaming issues, I only have one more thing that I wish to change about the distribution.
Bootup/Shutdown time.

I own a Lenovo T410S, with 120GB SSD, 8GB RAM, Intel i5-560m, 2.66Ghz dual core, 4 threads.

With Linux Mint and Ubuntu, the boot time was less than 5 seconds, and shutdown time was less than a second.

Now with OpenSuse 13.1 64bit KDE shutdown time was less than a second.
Boot time was about 30 seconds.

With OpenSuse 13.2 64 bit KDE, shutdown time is over 5 seconds(It is very annoying because if I close my laptop lid before shutdown, power-off gets stalled and the laptop goes into hibernation and drains battery rather quickly. Lenovo T410S is notorious for its’ lack of battery endurance)

Opensuse 13.2 64 bit KDE boot time is also around 1 minute. I have disabled the suspend on boot(prompting to ask for which kernel to use) already and the boot time is still about a minute.

I was wondering if there was a way to at least decrease the shut-down time. I an open to suggestions (Preferably tested).

From your story I get the impression that you mean with boot and shutdown, not only the sytem boot/shutdown, but aso the KDE login/logout. Now considering the end effect for you (having to wait for it) it might be rather pointless to give things their correct names, but when you want to speed up things it is rather important to diffentiate between the two where it only to find out which one of them takes the bulk of the time.

Thus first avice from me would be: time the boot, time the login and the same for logout and shutdown. When e.g. it is KDE that takes most of the time, there is no use to study your boot process in detail.

It does seem that the “log-off” at shutdown takes the most time. How would you recommend to reduce loading/unloading time for KDE?

Log-off on my system (but 13.1 and KDE) does not take that long normaly, but it depends of course very much on how many applications (and which ones) you still have open. They must be given a chance to shutdown properly. The same btw on log-in. When you have configured that applications open at shutdown should be restarted on login (or have some applications to start always on log-in), there may be much work to do (like starting KDE-PIM suite).

On the other hand, when you need those applications more or less “always”, stopping them manualy before logout and starting manualy them after login will not make the total faster of course.

Maybe you could, for a test, stop all on your destop before log-out and time what happens. Just to try to find what consumes the time.

hi @SJLPHI,

it would be helpful to see the output of cmd
systemd-analyze blame

jfi
1-2 seconds seem to be added to the start-up time per GB of RAM,
this depends on bios POST, cpu/clock speed. etc …

also noticed is that shut-down time is very dependent
on internet activity and journal settings
and can very between 1-30 seconds on the same HW

cheers

As standard, I shut down all open applications before I shut down the laptop. I am using some of the Gnome apps with KDE, and if I don’t do this, I get glitches sometimes.

The most time consuming portion at shutdown is that I get to

user login:

3~10 seconds later, some letters numbers automatically show up after login: then the laptop actually shuts down.

systemd-analyze blame


    1min 28.182s rc-local.service
           736ms postfix.service
           531ms apparmor.service
           383ms vboxdrv.service
           248ms SuSEfirewall2.service
           233ms display-manager.service
           182ms plymouth-read-write.service
           134ms ModemManager.service
           131ms SuSEfirewall2_init.service
           100ms dev-disk-by\x2duuid-34a31cce\x2d0ba3\x2d4d20\x2db74f\x2ddf27e8332183.swap
            88ms alsa-restore.service
            84ms systemd-user-sessions.service
            79ms bluetooth.service
            76ms avahi-daemon.service
            74ms nscd.service
            66ms wpa_supplicant.service
            62ms rtkit-daemon.service
            58ms udisks2.service
            55ms NetworkManager.service
            55ms systemd-tmpfiles-setup.service
            52ms systemd-udev-settle.service
            47ms systemd-udev-trigger.service
            44ms lvm2-activation-early.service
            40ms polkit.service
            36ms systemd-tmpfiles-clean.service
            35ms auditd.service
            34ms user@1000.service
            33ms cycle.service
            30ms systemd-fsck-root.service
            26ms lvm2-activation.service
            25ms systemd-journald.service
            23ms systemd-vconsole-setup.service
            23ms systemd-readahead-replay.service
            23ms dev-hugepages.mount
            22ms dev-mqueue.mount
            21ms systemd-readahead-collect.service
            20ms kmod-static-nodes.service
            19ms sys-kernel-debug.mount
            17ms plymouth-start.service
            17ms lvm2-lvmetad.service                                                                                                                        
            15ms dm-event.service                                                                                                                            
            15ms systemd-udev-root-symlink.service                                                                                                           
            15ms systemd-tmpfiles-setup-dev.service                                                                                                          
            11ms systemd-sysctl.service                                                                                                                      
            11ms systemd-remount-fs.service                                                                                                                  
             9ms iscsi.service                                                                                                                               
             9ms systemd-udevd.service                                                                                                                       
             8ms systemd-update-utmp.service                                                                                                                 
             8ms upower.service                                                                                                                              
             8ms systemd-logind.service                                                                                                                      
             8ms systemd-journal-flush.service                                                                                                               
             7ms systemd-modules-load.service
             5ms systemd-update-utmp-runlevel.service
             5ms systemd-readahead-done.service
             4ms systemd-rfkill@rfkill1.service
             4ms systemd-rfkill@rfkill0.service
             4ms systemd-random-seed.service
             3ms sys-fs-fuse-connections.mount
             2ms systemd-rfkill@rfkill2.service
             1ms systemd-backlight@backlight:intel_backlight.service



nothing looks out of place except for

1min 28.182s rc-local.service

can only suggest all services be verified as still needed
and de-activating those that are not