How to know the boot time of our computer with Systemd?

Systemd It is the new daemon for the boot system that many distributions incorporate that have replaced the old one init.


Hated by many (including Linus Torvalds who with good reason sent one of his programmers to fly), adored by others, it is still true that regardless of the problems that Systemd may "philosophically" have, the distributions that have adopted it have shown a boot time much lower than the rest.

And that's exactly what this post is about, showing you a simple command that will show us the Kernel startup time and the workspace.

We open a terminal and put:

$ systemd-analyze

In my case, I have ArchLinux installed on a Caché SSD, with KDE 4.12.4, so I got the following result:

Startup finished in 5.355s (kernel) + 2.309s (userspace) = 7.664s

What do you think?

The content of the article adheres to our principles of editorial ethics. To report an error click here!.

37 comments, leave yours

Leave a Comment

Your email address will not be published. Required fields are marked with *



  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   Maykel said

    Systemd seems to me the best, I have not seen anything like it. Also the systemctl status gives a lot of info to help correct certain errors. Look at mine:

    [maykel @ maykel-arch akonadi] $ systemd-analyze
    Startup finished in 1.785s (kernel) + 1.511s (userspace) = 3.296s

    I guess that if you say ssd cache, you use it only to load the OS boot and to cache the apps that you open to ssd cache. I have it all on the same 128 GB ssd.

    Thanks for the info.

    1.    elav said

      Cache SSDs are SSDs that some manufacturers include for Windows to use as Virtual Memory. I understand that they are cheaper and "bad" than normal SSDs. In the SSD Cache I have the System installed leaving my data for the mechanical disk 😀

  2.   petercheco said

    From the beginning I said that SystemD is one of the good things for linux. From the beginning I said that Debian will adopt it and the reasons are more than obvious. Btrfs is also it and therefore my servers, laptop and pc's are already on it. And I admit that very, very well 😀

    1.    B said

      And aren't you delighted with the new functionality of Btrfs (the addition of extended attributes)?

      It is true that there are not many (none, I would say) applications that use it, but the possibilities are endless.

  3.   axel1709 said

    it takes me a long time:
    Startup finished in 2.961s (kernel) + 24.178s (userspace) = 27.140s

    How do I make it start faster? Because I really do notice it

    1.    elav said

      You would have to install an SSD. 🙁

      1.    axel1709 said

        Well then I'll stay better like this hahaha

    2.    anom said

      systemd-analyze blame

      It tells you the time for each service

  4.   Adolfo Rojas G. said

    Startup finished in 3.605s (kernel) + 25.651s (userspace) = 29.257s
    How can I improve the startup time of my machine: ((I have kernel 3.8 and cinnamon as desktop environment, I'm on archlinux)

    1.    elav said

      Boot time will only improve using an SSD. Although at the Software level you can make some adjustments, an SSD is the solution.

  5.   Bart said

    KaOS startup time on a msata SSD:
    Startup finished in 1.082s (kernel) + 1.343s (userspace) = 2.425s

    A luxury!!

  6.   Damn bearded said

    In addition to the total time, options can be added to show more information:

    systemd-analyze blame sorts the time of all processes from highest to lowest
    systemd-analyze critical-chain indicates possible bottlenecks in startup times.

    A greeting.

    1.    elav said

      Thanks for the information..

  7.   day said

    Startup finished in 2.089s (kernel) + 6.680s (userspace) = 8.770s
    That gave me on KaOS with a mechanical disk, I think kaos is a cheaper fast boot solution than an ssd: p. Nor do I want to imagine when he started with one of those.

  8.   B said

    The truth is that the kernel takes a long time to start ... for what (theoretically) little it does. But hey, I think it's monolithic kernel stuff 😛

    The userspace thing is impressive.

  9.   Miguel said

    I have tried running the command but the answer it gives me is:
    bash: systemd-analyze: command not found
    I have Debian Wheezy installed.
    Since the order is not found, do I have to install something beforehand?
    Thank you very much for attention.

    1.    Yukiteru said

      As the article says, the command is for systems that use SystemD as init, in Debian Wheezy SysVinit is used so this command will not work for you, mate.

      1.    Miguel said

        Thank you very much for the clarification Yukiteru. One more thing one learns in this fascinating world of GNU / Linux

  10.   Aryans said

    7 seconds !!! tremendous. One question, did you do something special to install arch in this ssd cache?

  11.   Jesus Perales said

    Any advice on how to lower these times?

    Startup finished in 1.371s (kernel) + 4.005s (initrd) + 56.367s (userspace) = 1min 1.744s

  12.   NauTiluS said

    As always, around here, there are very good tips.
    According to the command, this is what it throws at me:

    Startup finished in 2.395s (kernel) + 26.193s (userspace) = 28.588s

    And what the bottleneck does, is this: @ 26.193s
    └─ @ 26.193s
    └─pdnsd.service @ 26.192s
    └─ @ 26.192s

  13.   Joseba said

    With a WD Blue 500GB
    Startup finished in 4.051s (kernel) + 11.885s (userspace) = 15.936s

    My bottleneck is 3
    ntpd.service @ 11.487s + 397ms
    NetworkManager.service @ 6.332s + 5.153s
    dev-disk-by\x2duuid-357098a9\x2daf36\x2d456c\x2dabe4\x2d7576d1792dfa.swap @6.091s +205ms

    The truth is that this worries me: S
    NetworkManager.service @ 6.332s + 5.153s

    1.    Joseba said

      Forgot to mention the distro. Manjaro with Gnome (community edition). And mechanical hard drive.

  14.   daviddoji said

    Startup finished in 3.266s (kernel) + 12.302s (userspace) = 15.568s

    and I do have an SSD! Although / home is on a mechanical disk.

    1.    edo said

      If you have it stored in a drawer I doubt that you will see any difference 😉

      1.    edo said

        I say it because I do not see that it is very fast

        1.    NauTiluS said

          And that, I have the mechanical disk and already with a couple of comfortable years of service. The disk in question is: Maxtor 6L250S0

          On the one hand, when I got this disk and according to tune2fs:
          Was created:
          Filesystem created: Tue Oct 12 11:28:03 2010

          And it has moved in all that time:
          Lifetime writes: 1353 GB

          Although, I know why the network-manager has that time, and the pdnsd depends on the latter to work.

  15.   xxxgAboxxx said

    Hello! I would like to know how to do this test in Mint ... Greetings!

  16.   Cristianhcd said

    not available in elementaryOS, what a shame, because we did a long time ago with some friends in fedora: '(

  17.   Marco said

    Startup finished in 2.111s (kernel) + 5.034s (userspace) = 7.145s

    some way to improve the userspace (I have to delete files ?? XD)

  18.   Fenriz said

    0.75 Seconds !!! WUAO

  19.   Grey said

    Thanks for the contribution friend

  20.   clow_eriol said

    In linux mint how would it be done?

  21.   AurosZx said

    Well I with an Intel E2140 CPU, 2GB of RAM, integrated GMA950 and two disks (SATA1 of 148GB where the system is, IDE of 40GB), I have this:
    Startup finished in 2.794s (kernel) + 17.784s (userspace) = 20.578s
    Nothing bad. By the way, Archlinux x86. My limitation is the disk.

  22.   arkan said

    $ systemd-analyze
    Startup finished in 1.731s (kernel) + 2.882s (initrd) + 4min 48.866s (userspace) = 4min 53.480s

    $ systemd-analyze blame
    4min 33.660s bumblebee-nvidia.service
    23.110s rsyslog.service


  23.   Phb said

    Hey how are you ... hey how I can reduce the userspace time, since it appears to me that they are 34.151s aaaww I already knew that it took a long time